That is right
So for example: base part is called CFG-TRLEDG, real part is called IA1032. This real part could be anything based on the configuration as we have all of these part numbers in our system already and determining the correct one based on lookups. How would I make this work using record creation, part creation? Sorry if this makes anything more confusing, a little new to this myself
Got it to work the way we want it to!!! Thank you for your help
Yash, there is a configurator technical reference guide on epicweb that will help you take advantage of all the features. I recommend you check it out.
Glad you figured out how to utilize the part creation piece of it.
Be sure to test, test, and test again. Sometimes you will use features of the configurator that do some awesome stuff, but it breaks built in logic throughout the application, much like BPMs and Data Directives can do.
Glad the problem was resolved. I saw I was referenced.
The way that the configurator works, you should NOT be changing the part number or the BASE part number with C# code in the document rules unless you really know what you are doing. When you manually changed the BASE part number, you basically disabled the configurator (unless the new BASE part number is also configurable). I have seen instances where we DID change the base PN intentionally, specifically if the results of the product was a non-configurable/stocked item.
Thanks for the additional info Tim!
So when we create the job for the part, the method pulls for the existing part number not the configured part where it should replace configured items. Is there a way around that?
Yash, I don’t know how your configurator is set up or what you are expecting. You write method rules on the method of the base part. When you click, get details, it should bring in the method according to the rules