I am converting a Classic Configuration to Kinetic version. The below code which retrieves all Inputs used in the Configurator is throwing error in the Kinetic Version. The control framework on being defined using Ice.Lib.Framework does not recognise the controls used in the configurator. I am also unable to find an Input List in the Kinetic.
Code:
Errors:
Configuators already had a small user base, and Kinetic Configuators is a even smaller group. I haven’t converted any of mine yet. I’ve started two times, but its so hard, so confusing, and so frustrating I gave up both times.
@Jkinneman seems to be pretty deep into it, the answer is pretty easy to guess… You probably can’t do that anymore.
Hi Rincy!
Where in the conversion process are you getting these errors? Are you receiving them on the Kinetic side post-conversion?
One thing that’s really tricky is a lot of the logic changes from Classic to Kinetic, so some UD methods might be using assets that are not present in the new version. Kinetic config is definitely a beast of it’s own and as Evan said above there aren’t too many of us that use embedded config so these situations can be tricky at times.
Regarding the input list, are you trying to see inputs for a single configurator or for all of them that you are trying to convert?
It looks like he is checking all combo boxes whose name ends with “_com” to see if they allow a certain choice.
In this particular case, I think the solution would be to move where the logic is for deciding what options are available in the drop down to a UD method, and then check the outputs of those UD methods directly. You shouldn’t be trusting what the client says the options for the combo’s are anyway. People could open the browser tools and add options. (etc etc)
Hi Austin,
So the Config UD Methods are in the classic version so it wouldn’t give a syntax error there but in the Kinetic Version, it recompiles all the UD Methods again in the designer- irrespective of if you have called them or not. I am receiving the errors on trying to save the configurator designer.
I am trying to see the Input List for a single configurator. I was expecting to find a similar list as we have in the Classic Designer.
Okay, thanks for explaining! That makes sense.
I’ve had similar issues when I bring over UD methods from PROD to our test/pristine database as well. I imagine it’s kind of similar to your issue. A lot of times, I’ve had to rebuild the UD methods from scratch or at least partially.
I’ve never converted any from Classic though, but I would imagine the logic/formatting has changed within the Kinetic configs which is causing the errors. You’ll find as you go along with the embedded configurator, that it’s very particular about what it lets you save/publish. If the logic/asset doesn’t exist in Kinetic, more often than not it’ll prevent you from saving entirely.
I’m not sure how much work it would be to rebuild these in Kinetic, but that may be your best bet. Maybe check with support to see if they have any tricks up their sleeve regarding this so you can save some headache/time if possible.
As for the Input List, I can’t say I’ve found any way to do that in Kinetic either. As far as I know, there’s no out of box way to do that, however I could be wrong. If you find it, by all means please feel free to share because it would certainly help!!
I hope this gets you on the right track. I’ll do some digging and experiment with some of our UD stuff to see if I can come up with something. But, just judging on the errors that you are receiving, it looks to me like the logic/field names/input structure is changed in Kinetic from how it was in Classic to where it can’t find where to point most of the UD methods.
