Please watch the section on the current bug with the October release before using this new feature! It's linked in the chapters for convenience. Once it's fixed I'll update this comment. 🙂 Also, I got a note from Cristian Prifti on LinkedIn that there's a bug with using measures.info for the dynamic formatting of a calculation group (if you're not sure what this is, then you likely won't bump into it!). Thanks for the heads up Cristian!
Ah great one, I just saw that you got a different video with API, and as you said, this is low code stuff =) Is there any approach to see which data sources have been used within each table/query? I managed to use some custom connectors with API, but is there any like "smooth" method to it? thx
Thanks! There’s a bunch more info() expressions that can pull more model info, but the ones in the video are the only ones you can display in a calc table right now. The API is a good place to get it, especially if you have that working already, but have you tried Measure Killer as a tool? It has a free version and works realllllly well to show you what you’re using and not using.
I got the Something went wrong error when trying to create the calculated Measures table and I noticed that when you run it in DAX query Veiw and there is one or more [State]='Invalid' I get the "Something wnet wrong" error. Once I fixed or removed the invalid Measure i could create the calculated table.
While this method is simpler, nothing gets unlisted 😂 The previous method will still be valid in my opinion (until live connection is supported) for creating centralized documentation across multiple models. 😁
At the very least it's useful until they fix the bug.🤣 If you like the multiple model concept, DEFINITELY check out the Power BI Admin API - it has everything in the tenant and its awesome. It's just a PITA to get it out. With my luck, about the time I manage to get a video done on that one they'll make it a one-button click in the service somewhere..
Please watch the section on the current bug with the October release before using this new feature! It's linked in the chapters for convenience. Once it's fixed I'll update this comment. 🙂
Also, I got a note from Cristian Prifti on LinkedIn that there's a bug with using measures.info for the dynamic formatting of a calculation group (if you're not sure what this is, then you likely won't bump into it!). Thanks for the heads up Cristian!
Ah great one, I just saw that you got a different video with API, and as you said, this is low code stuff =)
Is there any approach to see which data sources have been used within each table/query? I managed to use some custom connectors with API, but is there any like "smooth" method to it? thx
Thanks! There’s a bunch more info() expressions that can pull more model info, but the ones in the video are the only ones you can display in a calc table right now. The API is a good place to get it, especially if you have that working already, but have you tried Measure Killer as a tool? It has a free version and works realllllly well to show you what you’re using and not using.
I got the Something went wrong error when trying to create the calculated Measures table and I noticed that when you run it in DAX query Veiw and there is one or more [State]='Invalid' I get the "Something wnet wrong" error. Once I fixed or removed the invalid Measure i could create the calculated table.
Oh interesting! If you message Zoe Douglas on LinkedIn, she will send in a bug report for it (she’s the PM for this feature). Thanks for the heads up!
While this method is simpler, nothing gets unlisted 😂 The previous method will still be valid in my opinion (until live connection is supported) for creating centralized documentation across multiple models. 😁
At the very least it's useful until they fix the bug.🤣 If you like the multiple model concept, DEFINITELY check out the Power BI Admin API - it has everything in the tenant and its awesome. It's just a PITA to get it out. With my luck, about the time I manage to get a video done on that one they'll make it a one-button click in the service somewhere..
@@bi-ome I do like the admin APIs, but I tend to like the low code approaches since not all clients react positively to the admin APIs ideas 🤭