TAV
Well Known Member
Recently we had an issue where because we merged the specs on an ESU we ended up with code that was deleted from the JDE object still in our code and it caused major issues. Nice of JDE to actually delete it and not comment it out but so it happens and you have to live with it. I need a solution to how we can avoid this issue though and have a real base object set to test with. I basically think you should always have a base set to test against or at least compare against.
Asking CNC to un-select the merge option is apparently asking too much and it appears updating the Pristine environement with updates regularly is too much to ask as well. So here we are.
I have in the past always had a base code set (like Pristine updated with ESUs taken) to compare against and this made making sure the base code worked pretty easy. However, my current location has Pristine as the base code delivered without any update and this is useless.
So I need to present a solution that will not overly tax CNC resources but be useful. However, any feedback on how Pristine can be used as a base code set or other solutions that accomplish the same thing will be greatly appreciated.
Thank you in advance,
Asking CNC to un-select the merge option is apparently asking too much and it appears updating the Pristine environement with updates regularly is too much to ask as well. So here we are.
I have in the past always had a base code set (like Pristine updated with ESUs taken) to compare against and this made making sure the base code worked pretty easy. However, my current location has Pristine as the base code delivered without any update and this is useless.
So I need to present a solution that will not overly tax CNC resources but be useful. However, any feedback on how Pristine can be used as a base code set or other solutions that accomplish the same thing will be greatly appreciated.
Thank you in advance,