I'm having trouble packaging out custom system settings and their values. I have two entries for data in my package. One for the SysSetting entry and one for the SystemSettingValue entry. Upon installing the package, I can see the values as they should in the Database, but in the UI, the setting entry is there, but the value for the setting is not. I tired clearing the Redis Cache, but that didn't help.
What is the correct procedure for packaging out system settings?
Thanks!
Like
Hi Jeremy,
Adding data for SysSetting and SysSettingValue are the correct things to package for system settings - I package those frequently and never an issue. Could it be that the SysSettingValue data record isn't including the correct fields? Can you see a record related to the SysSetting record in the SysSettingValue table? Maybe it's not showing the value in the UI because the correct columns aren't being included? (A SysSettingValue record uses one of multiple different fields depending on the datatype of the setting). Could that be the case?
Ryan
Hi Ryan
Yes, there are records in both tables joined by Id-->SysSettingsId. It's a Text value and there is a value in the Text field on SysSettingsValue.
I added a value to the setting in the UI and it created another record in SysSettingsValue for that SysSettingsId. Only diference I could see is that the original entry had a Null for SysAdminUnitId. Sure enough, after I set that value in the DB, my original value started showing up in the UI.
I looked at the source system and target system and they both have the same SysAdminUnitId in the SysAdminUnit table.
I ended up decompiling the package to see if the value was in the Data step for SysSettingsValue and it was not.
Any idea why just that value would not copy over?