Archive

Archive for December, 2021

Power BI | Dataverse | Fixing the connection reference of a report

December 31, 2021 Leave a comment

For the unversed, Using ‘Power BI embedded’ we can embed a Power BI report as Dashboard in Model Driven App.

This Dashboard can be added to a Solution and can be transported to other Environments. However there will be a challenge with report’s Connection reference.

When the Dashboard moved to another Environment, the connection will not be refreshed with Target Environment and will be still pointing to Source Environment.

As an example, if the Power BI report was built connecting to ‘DEV’ Environment, when the report exported from ‘DEV’ using Solution and imported to another Environment, reports connection will be still pointing to the Source Environment (i.e., DEV).

Workaround to refresh the Connection:

  • At the time of writing this article, there is no straight forward option to refresh the Power BI report’s Dataverse Connection.
  • One option is Save the Power BI report (i.e., .pbx file) locally and create a copy and rename.
    • In my case, I’ve renamed ‘Account_DEV’ to ‘Account_TEST’ file.
  • Open the ‘Account_TEST’ file and open the ‘Power Query Editor’ by selecting ‘Transform data’ option.
  • From the ‘APPLIED STEPS’, select ‘Source’ and update the Dataverse URL.
  • Save the report and publish to Power BI ‘Workspace’
  • Assuming you have moved the Report from ‘DEV’ to ‘TEST’ environment using the Solution, as a last step, connect to ‘TEST’ environment and select the report.
  • Click ‘Edit’ and select the ‘Account_TEST’ report from ‘TEST’ workspace.
  • This manually correcting the report’s connection works. I believe in near future we will have much easier and straightforward approach to refresh conenction.

🙂

Categories: Power BI Tags: , ,

Power Apps | On-premises data gateway | High-availability Clusters

December 27, 2021 Leave a comment

In one of my previous articles, I detailed the steps to connect to an on-premise SQL server from a Canvas App.

High availability: Refers to a set of technologies that minimize IT disruptions by providing business continuity of IT services through redundant, fault-tolerant, or failover-protected components inside the same data center.

By default On-premise Gateway is single instance and not a High availability option. If the gateway is unavailable, data requests will be failed and causes App downtime.

In this article, lets see how to build an high available On-premises Gateway using Clusters.

Gateway Clusters:

  • A cluster lets gateway admins avoid having a single point of failure for on-premises data access.
  • If the primary gateway is unavailable, data requests are routed to the second gateway that you add, and so on.
  • Following is the option to add a new Gateway to add to an exiting Gateway Cluster.
  • Because we can install only one standard gateway on a computer, we must install each additional gateway in the cluster on a different computer.

Refer this Docs article for more details.

🙂

Categories: PowerApps Tags: , ,

Model Driven App | Power BI | Visualize data

December 22, 2021 Leave a comment

There’s a new way to visualize your model-driven Power Apps and Dynamics 365 data stored within Dataverse. With a single click, Power BI will automatically generate a set of visuals for you to explore and find insights within your data.

Prerequisites:

Enable Model Driven App Level Setting:
  • This feature is App specific, so select the Model Driven App and choose ‘Edit in preview’ option.
  • Go to Settings -> Features and enable “Enable Power BI quick report visualization on a table (preview)” option.
Enable Environment Level Setting:
  • Go to Settings -> Product -> Features
  • Enable ‘TDS endpoint’ feature.
Power BI License:
  • Make sure you have Power BI license.
  • If you dont have a license, ‘Visualize this view’ shows following screen.
  • Acquire license and retry.

Using ‘Visualize this view’ option:

  • Open the Model Driven App.
  • Select any view and click on ‘Visualize this view’ button from Ribbon.
  • It will open up, Power BI report screen.

Key Notes:

  • The data being visualized within the report is always based on the data currently in the view’s grid.
  • This means if you’ve applied any filters to the grid, that filtered data will be used in the Power BI visuals. For example, if the view is filtered down to just 15 rows of data, only 15 rows will be visualized through Power BI.
  • At the time of writing this article, the visuals generated from this flow can only be used for personal exploration. You can’t share or save them.
  • Column display names aren’t used within the report. You’ll see the system names in the resulting visuals.
  • You may notice more columns within the report than you see in the original view. These fields could include foreign keys for the columns or hierarchy, or URL fields that are being used within the original view for purposes other than columns.
  • The report created through this feature is temporary, so the experience times out after a set amount of time. At that point you need to close and reopen the report to continue exploring your data. For now, the timeout occurs at one hour.

Refer this docs link for more details.

🙂