Magaya Ideas Portal
Problem statement
When Custom Fields are exported to XML and imported into another database, some configurations are not included. For example, Pick List values and Calculated field logic are missing after the import. This means users must manually recreate those configurations in every database where the field is needed, which makes environment setup and replication time-consuming.
Description
The goal of this improvement is to allow Custom Field definitions exported via XML to include all the necessary configurations so that fields can be recreated completely when imported.
Previous Title of this Idea:
Extraction of customs fields in XML.: Include the script codes in the tree structure of the XML file when extracting the customs field CALCULATED for a complete and efficient import
Description
We are facing a problem with the integration of customs fields that we have performed in ID 38413 and replicated in 38482 + 31556.
After verification, we observe that the customs fields with a calculated field are not correctly included by XML. file.They are imported by default in TEXT mode instead of CALCULATED, and impossible to modify manually, the field is greyed.
To date, LVO must remove these imported CALCULATED customs fields and recreate them manually in each database. (related case 275221)