I am working on several Kinetic Configurators for clients and continue to be frustrated with its current state. Some bugs lead to lost work while others require work arounds or at a minimum explaining to clients about the odd behavior.
Main advice is save early and often. In prior versions of Epicor saving was rarely needed as the configurator even if you didn’t want it to did saves after pretty much any action. Not so in Kinetic, so you need to remember to save.
For example if you add a new control and don’t save and then go into another control’s on change event, that control will not see the new control you just added until you save.
Second reason is the configurator designer will lock up from time to time requiring you to exit and come back in. Any work since the last save is likely gone.
If you use the property search to locate a single property and that search results in one result if you select another control the designer will freeze and only way to recover is to exit and come back. If you haven’t saved, any new work is lost. Remember to cancel you search before clicking anywhere else.
If the configurator in the designer isn’t doing what you think your code should be doing, save, exit and come back in.
Remember to publish. Approving isn’t enough, you have to publish. I have gotten into the habit of approving and unapproving only in the designer.
Do more exports.
One bug that is really annoying is args.Cancel doesn’t work to prevent user from exiting if you are validating things on page leave. Work around create a text box, make it required, make invisible. Populate it programmatically if things are good, leave it blank if not ready to leave. You will need to explain to your users what the message means. I usually pair it with a text box that lists what still needs to be done with a label that says “Must be empty to save”
Edit client side user defined methods in the designer. The menu user defined methods will be confused with use of the “await”. With that said they only place you can build server side UD methods that use the “out” and “ref” modifier is in the menu UD method screen. You can’t call server side methods that use the “out” and “ref” modifier from the client but thankfully you can call them on the server side from method and document rules. If we couldn’t I would likely consider retiring.
