@TI 

I looked into the KB and help files, but there is no mention about a version free variable in a datacard being reset to an empty field when a new configuration is added. EVEN WITH UPDATES ALL CONFIGURATIONS ENABLED.
It does not sound right, because all the datacard content should be copied from @ configuration to the new one. 

Our VAR tested in a empty default vault a sample datacard with two fields:

1. New file is created
2. Versioned variable field value input as “XXXX” in the datacard
3. Version Free variable field value input as “YYYY” in the datacard
4. File is checked in
5. datacard shows the “a“ configuration tab with “XXXX” for the versioned variable and “YYYY” for the version free variable field
6. File is checked out
7. Configuration “a” added from the configuration tab in the property manager
8. File is checked in
9. datacard shows the “a“ configuration tab with “XXXX” for the versioned variable and EMPTY for the version free variable field, other configurations still shown as “XXXX” and “YYYY”as expected.

Same datacard settings for both variables, “Updates all configuration” enabled, default value empty, default overwrites disabled

Same behavior for SW 2022,2023 and 2024.

Personal note: the wording in the manuals and technical docs is suggesting that “Updates all configurations” works during the input phase of the card, that use is OK and the results are copied over the configuration AFTER the input. The problem here is the creation of a new configuration should carry on all the values from the old one for consistency otherwise one tab has a different (empty) value and it could potentially trigger a input mistake that deletes the correct field in the other configurations.