Replies: 3 comments
|
Good point. DQ models and especially DQ over AS models are rarely opened in Tabular Editor, so there’s probably a bunch of stuff we can do to improve the experience overall. |
0 replies
|
A pure DQ model I would agree, but a composite model with a mix will likely become increasingly common. I hit this today trying to debug an issue and was having trouble keeping the table origins straight. Thanks! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Suggested UI enhancement.
Have some indicator for the tables that come from a DQ source vs import, and potentially even a numerical or alphabetical indicator of the model. In the image below Employees is from a different AAS source, but other than looking at the details and compariing GUIDs no way I can see to know.
Maybe another column that has the dataset name in this view?
But even a table icon with a little link or lighting bolt to quickly distinguish form import tables.
All reactions