Need a little refresher on the differences between the System Settings “Current package” and “Custom package Id” and how they work together. Documentation on the System Settings explains the “Current package”, but no reference to the “Custom package Id”. By the documentation, the Current setting allows me to save any section changes to that package set in the setting's value (usually a new package that is portable e.g. “MyOwnCustomPkg”). I also understand if Current is not set, the section changes get saved in the platform’s “Custom” package by default. However, I don’t understand the true use of the “Custom package Id”. How is the “Custom package Id’ used if the Current setting is set? Does the system use both and if so, how and when and for what objects?
In other words, how are these leveraged?
Documentation Link: https://academy.bpmonline.com/documents/studio/7-10/system-settings-description#XREF_62576_6_1_3
Steve
Like
Dear Stephen,
The usage of Custom Package Id system settings is reflected in this article - https://academy.bpmonline.com/documents/technic-sdk/7-10/package-custom. The setting is used when you need to make Custom package a root package in the system. So, this is the system settings you need to refer to if you want to set up the dependencies between the packages so they would reflect the custom logic.
Lisa
Lisa,
Ok, the documentation explains the Custom package fairly well and I follow that, but how do these two settings work together? If I set Current package to my own package for development purposes (e.g. to save in SVN etc..), then all section changes via the wizards get saved to my package and not “Custom” correct? So what use is the “Custom package Id” when I have done this in the Current setting? Is "Custom package Id" simply to always declare the root? Why are there two settings?
Steve
Dear Stephen,
These setting do not work together at all. If you are interested in the setting to be able to save all the customizations to the specific package, you need to go for 'Currecnt Package' one. When you apply the changes to the 'Current Package' custom package settings are not influenced in any way. Moreover, we do not recommend to change the value in the 'Custom Package' system settings at all, since it can influence the whole system.
I understand that having two setting with the similar names may be confusing, thus I have created a request to our R&D team to improve the functionality (and possibly get rid of the 'Custom Package Id' settings) in the further releases.
Thank you for your feedback.
Lisa
Thanks Lisa. In the meantime, updating the documentation for the systems settings would be very helpful, especially a defination of "Custom packege id" and best practice as you suggested.