Erwin Development has identified a problem in Mart Server v. r9.64 and r9.7 when saving changes to a mart. This problem is not reproducible in all environments and it only occurred when a model in the mart had been modified by more than one data modeler at the same time and a three-way merge was required:
1. Calculated values.
Column names were not renamed. This problem occurs when a model in the mart is a newer version than the one we trying to save. All changes are loaded and applied but changes to the calculated values were explicitly skipped. If the modeler has made a change from the old calculated value to a new value, the loading of the mart model was not reversing the new value when constructing the model from the mart, and the merge was fooled into thinking the old and new values were the same and did not need to be saved.
2. Datatype changes for SAS database.
Some datatypes for SAS had unusual equivalence calculations. For example, NUMERIC was equal to DATE, and the number after CHAR(10) and CHAR(20) were not compared. Although the models on both sides of the merge were different, they compared as equal.
3. Data source changes.
The result of the comparisons of the SET-type of property was reporting only the result of the comparison of the first item in the set. E.g., for sets of DATASOURCE REF 123, 124 was the same as DATASOURCE REF 123,125.
In addition to the above fixes, a lock is now enforced when a user starts to save a model to the mart and the lock is released only after the user finishes the save. The change avoids other modelers futilely attempting to save their changes at the same time, especially for large models, which would just result in a later warning that the model is currently locked so they should try to save later.
The above fixes will be included in the Mart Server software version after r9.7. In the meantime, r9.64 and 9.7 customers may contact Level One Support for a copy of the fix to be applied to their erwin Workgroup Edition r9.64 or 9.7installation.