Null value in Environment Specific Constant

RE: Null value in Environment Specific Constant

Mike Schmitt — Thu, 03 Apr 2025 13:48:03 GMT

There's a reasonable workaround to deploy a "default value" of environment specific constants to higher environments without needing a Properties file, and this sounds like a good use case for using this workaround:

create the constant in your dev environment with exactly the default value set how you want (clearing out any dev-specific data or setting if necessary)
UNCHECK (if needed) the "environment specific" checkbox in the Dev copy
deploy the constant (on its own) to all higher environments
CHECK the "environment specific" checkbox in the Dev copy
deploy the constant (again by itself) to all higher environments again - their "environment specific" setting will now be changed.

RE: Null value in Environment Specific Constant

Vyshnavi Naripeddi — Thu, 03 Apr 2025 03:19:26 GMT

1. In the lower environment, where you have the array of dates constant defined, leave the constant value empty. Do not provide any values in the constant. 2. When deploying to the higher environment, in the custom properties file, do not provide any value for the constant. Leave the property value blank.

For example, in the custom properties file, the entry for the date constant would look like this:

date_constant=

By leaving the property value empty, the constant in the higher environment will be deployed as a null value, as desired.

RE: Null value in Environment Specific Constant

Pablo Esteban Alvarez — Wed, 02 Apr 2025 09:12:08 GMT

If you leave that line of the properties file commented with #, I'd say it will deploy the constant the way you're looking for. If not, I would try to declare it as null, not sure tho.

RE: Null value in Environment Specific Constant

kapilsharma — Tue, 25 Mar 2025 10:05:36 GMT

Hi GautamShenoy ,

Yes you can update the value of environment specific constant via custom properties file
which you need to use during deployment
Within the custom properties file, look for the constant and update its value after removing the HASH(#) from the beginning of the line.

Once the constant has been deployed, you can use it to update it via process model.

Hope that's helpful