Power Apps Visual for Power BI - CDS Direct Query Mode

[Syndicate_Admin]

Power Apps Visual for Power BI - CDS Direct Query Mode

In this video we will use the Power Apps visual in Power BI to add/update data in CDS using Direct Query Mode.

The Power App will refresh the Power BI report instantaneously and provide a virtually unlimited refresh scenario.

The Power BI report is using CDS with direct query mode to not rely on scheduled refreshes or imports.

SharePoint Import Mode is also covered as part of this video.

Setup CDS for Direct Query

https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/view-entity-data-power-bi

Direct Query Vs Import Vs Live Connection

https://docs.microsoft.com/en-us/power-bi/connect-data/refresh-data

https://www.youtube.com/watch?v=y4S-k34qmnw

https://radacad.com/directquery-live-connection-or-import-data-tough-decision

List of data sources and their supported refresh types

https://docs.microsoft.com/en-us/power-bi/connect-data/power-bi-data-sources

--------------------------------------------------------------------------------
Thanks,
Reza Dorrani, MVP
YouTube
Twitter

[rjhale]

This was really helpful for us to test using DQ to a CDS entity.  The report that we had been using this approach in was working fine for the past 5 weeks or so, but as of this morning we're seeing the following error when we load the report in the Service:

• Underlying Error: PowerBI service client received error HTTP response. HttpStatus: 400. PowerBIErrorCode: QueryUserError
• QueryUserError: Index was outside the bounds of the array.. The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action.

The individual visuals show the same "index was outside the bounds" error message.  Everything works as expected in Power BI desktop though.  We've tried republishing, resetting permissions, etc, but that error persists in the report where we're using DQ to a CDS entity. 

I know this is still in preview, but was there a recent change that would cause this?  Any other suggestions to work around this error? 

[EStieg]

This is great Reza, thank you for sharing!

Eric

[Syndicate_Admin]

Thank you

[Syndicate_Admin]

Thank you