@utaylor yes we did. We capture the ‘target part’ or what we call ‘base part’ and save that to a global variable. In subsequent sub configurators we bind that global variable to an input that is hidden in a second page of each configurator (what we called our debug page). That way we can use it in the logic for the current configurator to make decisions. We also built a line description that is made from all the choices in all the configurators in the method. To do that we also use a global variable and store in it a dictionary string which we parse out to get any of the information. Again, we also use that for making decisions in sub configurators. Pretty handy.
Much easier to explain in a short video. Here is an example of one of our configurators with sub configurators. At one point i will go to our hidden debug page and highlight our dictionary string and model number (target part).
Yes, the configurator is running slowly. that is because I am doing this on a system i have yet to apply the Windows fix for speed.
You may also notice i don’t choose something from every drop down. If there is only one option to choose from in a dropdown, i have it auto selecting that one item.