We would like to be able to separate content and maintenance so that a table/entity in project/model 1 can be referenced in another, but not updated. You already confirmed that diagrams within a model can reference shared objects, for example a table in the relational designer. I believe this means that all content of a large set of inter-related tables/entities would need to exist in a single model. This could work for us if there were features for restricting access to diagrams or other groupings of content, although across models would be ideal.
André GenMyModel
We would like to be able to separate content and maintenance so that a table/entity in project/model 1 can be referenced in another, but not updated. You already confirmed that diagrams within a model can reference shared objects, for example a table in the relational designer. I believe this means that all content of a large set of inter-related tables/entities would need to exist in a single model. This could work for us if there were features for restricting access to diagrams or other groupings of content, although across models would be ideal.
Jeff P.
1 person likes this idea