Planning Data Export/Import Improvements
This feature provides improvements to the Export/Import Feature.
XID is not matching with GID
This feature is to address issues where the exported data had XID which was different from GID. There were instances where the exported data's GID was <Domain_Name>.123 and XID was not 123 (any other value). This feature will update XID based on the GID value, if there is a mismatch.
Example: Original Data
| GID | XID | DOMAIN |
|---|---|---|
| OTMTEST.123ABC | ABC123 | OTMTEST |
Import Data (after this change)
| GID | XID | DOMAIN |
|---|---|---|
| OTMTEST.123ABC | 123ABC | OTMTEST |
Convert Invalid characters used on GID to OTM supported Characters
This feature is to address issues where the exported data has few special characters in GIDs and these data is failed while importing into OTM. This feature will replace those special characters to OTM supported characters while importing data into OTM.
- All the special characters in GID, XID and foreign keys will now be replaced by an underscore(_) during import.
- The special characters include :-
- , > < = / & ? ; # $ ' " ( )
- The data will be updated only if it is NOT Public data.
- The list of special characters is set using the reserved property :-
- glog.business.planningstreams.specialCharacters
- The substitute character is set using the reserved property :-
- glog.business.planningstreams.substituteCharacter
- If the property, "glog.business.planningstreams.substituteCharacter" is set to empty string, these changes will not take effect and the application will behave as before.
The import process fails because of such data. These changes will reduce manual work required by support team to fix the data while/during import.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
The Export/Import feature is found by navigating to Operational Planning > Planning Data Import/Export. Note: This menu option only appears for DBA.ADMIN users.