Workaround for Computed Entity in Power BI Pro: Dataflow in Power BI
I have previously written about What dataflow is and scenarios of using it. I also wrote an article about Computed Entity and the important role of that for performance and data lineage. However, a Computed entity is a premium-only feature. There are sometimes that you don’t really need premium functions of Power BI, and only the need to use a computed entity might be restrictive then. You want to reference another entity, and then you need a Computed entity as an example. In this article, I show you some workarounds that you can use to get the work done, without the need for a Computed entity, and even use it with normal Power BI Pro accounts. If you want to learn more about Power BI, read Power BI book from Rookie to Rock Star.
Read the rest of the article from here: https://radacad.com/workaround-for-computed-entity-in-power-bi-pro-dataflow-in-power-bi
FinTech | Financial Markets | Data | Analytics
5 年Thanks for the workaround Reza! Am not sure if had this issue, when executing computed entity, say merge between a table coming from dataflow and other table from a different source in pbi desktop. When the dataset is published to service and refresh is being triggered, a strange error appear “The columns parameter must be null, specify the number of columns, specify a list of column names, or specify a table type” could this be related to Premium at all?
BI Consultant, Speaker, Trainer & Author
5 年Excellent post Reza Rad, as you already mentioned in the article that maintenance cost for this method is high, is there a way we can share M code between queries, like storing a shared M code just like reference query without needing a Premium