Guidelines to avoid data corruption problems in MDMCE

Best practices to avoid data integrity issues (corruption)

1. Avoid running concurrent import or report jobs that modify items in the same catalog or collaboration area if possible.

2. Avoid modifying specs after there are already items defined according to the original spec definition in the catalog or collaboration area.

3. If you must modify the spec related to a collaboration area with items in it, try to empty the collaboration area prior to making your change(s).

4. If you absolutely must modify a spec where there are catalog or workflow items already defined, here is a list of safe versus unsafe operations:

Safe:

-adding a new attribute to the spec (making sure no items are in collaboration area)

-changing a currency attribute to a number (or vice versa)

-adding a new step to a collaboration area

-changing a string enumeration to string (or vice versa)

-changing a number enumeration to number (or vice versa)

Unsafe:

-changing a multi-occurring attribute to a grouping node with multi-occurring attributes under it

-modifying a workflow step with items in it

-for a catalog, changing an attribute's type to a different type when there are already items existing with values, except for those changes deemed safe (see above)

-for a collaboration area, changing an attribute's type to a different

-type when there are items currently in the collaboration area, except for those changes deemed safe (see above)

-changing a multi-occurring attribute to a singly-occurring attribute

-for a multi-occurring attribute, reducing the value of (max-occurrence - min-occurrence)

Note: This technote contains scenarios that are known till now and can be updated in future.