Summary
txc data model convert currently emits every attribute and relationship of every table in the solution. For ERD-style outputs (DBML especially) this is noisy — the out-of-the-box Dataverse attributes and system relationships bloat the diagram and bury the custom model you actually care about.
We'd like a way to control which attributes end up in the output, e.g. include only attributes matching a publisher prefix plus a few named exceptions.
Expected behavior
An opt-in option on txc data model convert to specify which attributes to include, likely as a list of name patterns:
txc data model convert --target dbml --include-attributes "myprefix_*,ownerid,statecode"
- Omitting the option keeps today's behavior (everything included).
- Applies across all output formats, not just DBML.
- Must not break the diagram — primary keys and the columns backing kept relationships should survive regardless of the filter.
Summary
txc data model convertcurrently emits every attribute and relationship of every table in the solution. For ERD-style outputs (DBML especially) this is noisy — the out-of-the-box Dataverse attributes and system relationships bloat the diagram and bury the custom model you actually care about.We'd like a way to control which attributes end up in the output, e.g. include only attributes matching a publisher prefix plus a few named exceptions.
Expected behavior
An opt-in option on
txc data model convertto specify which attributes to include, likely as a list of name patterns:txc data model convert --target dbml --include-attributes "myprefix_*,ownerid,statecode"