Restricting update of system properties in scoped applications
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-24-2025 09:33 AM
While building scoped app, we created few system properties. While promoting to higher environment, we don't want system properties values to be overwritten. Like System properties in dev should have dev credentials and QA should have QA
How can we achieve that?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-24-2025 11:22 AM
Did you try "Private" setting on the system property? I did not test it, but that could do the job maybe in scoped app and app repo (despite the docs mentions only update sets). I assume you are deploying the scoped app using App Repo.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-24-2025 11:36 AM
Private did not work for scoped application. Yes. I am using App Repo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-24-2025 12:53 PM
That is a pity. I am curious to see if any good solution exist. I can think of these workarounds a) Fix Script (having it run during installation to ensure proper values are set based on instance name), or b) Try to remove the properties from the App and deploy them via update sets, they might need to be in separate scope to have this working, or c) use update sets for deployment. Nothing great right?
