The feature is exists.
The developer is adding a Custom Field with the Default value.
Actual result: When the new bundle is installed in the ENV, the Custom Field has appeared, but with an empty value. Removing/adding a feature is needed.
Expected Result: Default value should be populated.
Alina Siomukha
| Categories | Feature Configuration |
| I need it... | Yesterday (let's go already) |
Hi. This is true statement.
But the problem happens if this is a disabled field with the default value.
Editors cannot change it.
We're using disabled field technique to show which CS is used.
Hi Alina, In order to serve the use cases of all our clients, we will not be implementing this functionality. We recommend that when a feature developer is adding a custom field with a default value that they put the new default value in the feature code which will get this result without needing to remove/add the feature. Thank you.