fysical data modelling not backward compatible

[vermeirl]

Recently upgraded to v17. We find that when creating an association from a newly created "table" to a "table" that was created in a previous version, the association cannot be defined as a "foreign key". The error says that source and target must both be tables (which they are). Even existing FK relations that were created years ago give the same error message.

[Eve]

What stereotype does the old table have? I'm guessing it's coming from an incompatible profile. Some older versions of EA were less rigorous about which stereotype was defined. That paired with more permissive checks in other places were also causing issues.

[vermeirl]

All objects involved have stereotype "table" (as in t_object.Stereotype). We are guessing the source of the problem is the "Stereotypes" entry in table t_xref. They all have "Name=table", but new objects have property "FQName=EAUML::table" (which we're guessing stands for Fully Qualified Name) whereas older tables have "FQName=EAUI::table" or no FQName property at all. Something like a "namespace" issue? We have noticed that "DB2::table" also exists (we are using DB2), so we are now very confused what it should be.

[Geert Bellekens]

They all should have EAUML::table

Geert

[Sunshine]

They all should have EAUML::table

Geert

Which indicates the fix would be to run a script and set all the stereotypes to EAUML::table.
Posted a script a while ago to convert stereotypes.
https://sparxsystems.com/forums/smf/index.php/topic,45674.msg267977.html#msg267977

Just need to change the line
Conversions[0] = new TypeConversion("Class", "Standard", "Class", "Motivation::Standard");
To
Conversions[0] = new TypeConversion("Class", "table", "Class", "EAUML::table");
That should convert any stereotype with Table to the correct EAUML. Just select the parent package where all the tables are and run the script.
Suggest trying it out on a copy to test it first rather than the production DB.