You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But instedad off individual files, then it can be condensed into one big JSON file that only focus on the object types that have dependencies to the underlying data model:
VisualObjects
PageFilters
ReportFilters
VisualFilters
Here is a suggestion to the layout of the output.
It's important to also include the information about the connection so that the ObjectKey can be created, when the report is in live connection mode. This might not be so straight forward, as it only contain the datasetid? In my use case I have the reports organized in folders, so I can deduce the name of the model.
My goal is to combine the information with the metadata from the datamodels, so I can create a Power BI report that shows the lineage/dependencies between reports and data models.
I get the model metadata (measures and columns) from this Tabular Editor script: https://www.elegantbi.com/post/extractmodelmetadata but could just as fine get it with an export from PBI tools. But that might be another feature request?
If it's easier to develop outputting individually files like the Tabular Editor export script from Michael Kovalsky, then I'm fine with that. Maybe just the same output as mentioned here: https://www.elegantbi.com/post/exportreportobjects
No description provided.
The text was updated successfully, but these errors were encountered: