Modify/Update the Synchronization Format
Article ID: KB0079090
Updated On:
| Products | Versions |
|---|---|
| TIBCO MDM | 9.0.0 |
Description
We may observe below issues while modifying the sync format.
Please refer the resolution category for each issue respectively.
| 1) When we update/modify the sync format and output map with new attributes in studio project once the record is published.After the changes,If we deploy the sync format we may get an exception like "Synchronization format name SF_XXXX already in use. Specify unique name". 2) Once the deployment is done with modifications of sync format/output map,if we re group the attributes within repository and deploying it will succeed.But,While deploying the sync format without any changes,We may get an exception as "Error while deploying Sync format: CAT-1013: One or more duplicate attribute names. Specify unique names".But the catalog do not have any duplicate attributes. |
Issue/Introduction
Unable to update/modify sync format and output map with new attributes in studio project once the records are published
Environment
ALL
Resolution
1) The resolution is a bit of risk as it modifies the metadata and there is no way to reverse it. To mitigate the risk we have introduced a config value under miscellaneous (com.tibco.mdm.syncformat.modify.aftersynchronization) to enable user to modify the sync format.By default it is false and also user needs to explicitly add this to config Values.This has been included through 9.0.0 HF-08.
<ConfValue description="This property enables to modify SyncFormat even after Synchronization" isHotDeployable="true" name="Enable JMX Stats Copy" propname="com.tibco.mdm.syncformat.modify.aftersynchronization" sinceVersion="9.0" visibility="Advanced">
<ConfBool default="false" value="true"/>
</ConfValue>
2) To avoid this issue we need to delete the respective deployed output map from MDM UI and redeploy the sync format into MDM server.
<ConfValue description="This property enables to modify SyncFormat even after Synchronization" isHotDeployable="true" name="Enable JMX Stats Copy" propname="com.tibco.mdm.syncformat.modify.aftersynchronization" sinceVersion="9.0" visibility="Advanced">
<ConfBool default="false" value="true"/>
</ConfValue>
2) To avoid this issue we need to delete the respective deployed output map from MDM UI and redeploy the sync format into MDM server.
Additional Information
Attachments
Feedback
Yes
No
Powered by
