Attribute renaming and MxModelReflection / Excel export

When I rename an attribute in the model the column in the excel export appstore module gets lost. This is caused because the synchronisation is done on name, could using ModelGUID solve this?
1 answers

It is correct that the module currently searches by name, and thus if you rename something the old attribute, entity, or relationship gets removed and a new item is created.

When model reflection was build the property ModelGUID wasn't available in the API. Until now I hadn't even noticed that it existed. Maybe somebody from R&D can clarify what it is and if this is always going to be the same for all domain model components. The javadoc doesn't explain what this is either.

If this property really is a static identifier it would be a much better candidate than the name to use for synchronization of the model.