Info.Datasources DAX Function Usage

[rjhale]

Hello,

I'm attempting to use the new DAX function Info.Datasoureds() for the first time.  I attempted to use this in the DAX query view in a pbix that has a number of queries loaded to the data model, but the function returns a completely empty table with columns such as ID, ModelID, Name, Description, Type, ConnectionString, etc.  I also tried connecting to several published semantic models using analysis services and running a DAX query that calls that function, but again, those return blank tables. 

Does anyone have any suggestions on how to use this function or if I need to call it in a different way to return metadata about the sources used in each model?  I was hoping I could use this as a way of easily pull in data source information across a lot of models spanning a dozen or so workspaces.  

[v-tianyich-msft]

Hi @rjhale ,

Thanks for @lbendlin  reply, here's a relevant sample you can refer to:DAX query view introduces new INFO DAX functions | Microsoft Power BI Blog | Microsoft Power BI

Hope it helps!

Best regards,
Community Support Team_ Scott Chang

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

[lbendlin]

EVALUATE

    INFO.PARTITIONS()

[rjhale]

Thanks.  That's good to know.  Do you have any other insight into why INFO.DATASOURCES function returns blank values? 

Also, I don't suppose there is a way to get the connection details for queries that don't get loaded directly into the model?  For example, we may merge data from a power bi dataflow with a SQL source, but that dataflow query will have "Enabled Load" disabled.   

[lbendlin]

Evaluate INFO.EXPRESSIONS()

[rjhale]

Interesting.  That does look promising.  

Before I mark this closed though, can someone explain what INFO.DATASOURCES is used for or how to get it to return values? 

[lbendlin]

The documentation on that on is, uhm, sparse.

[MS-SSAS-T]: TMSCHEMA_DATA_SOURCES | Microsoft Learn

[rjhale]

Right. I was seeing the same thing.  That's why I posted here, and I was hoping someone from Microsoft might weigh in with more info about intended use, a roadmap, or something like that.