Matrix (PQ vs PA, Dataverse vs Studio)

Matrix (Power Query vs Power Automate)

Matrix (Dataverse vs Microsoft Studio)

Matrix (Connecting through Power Automate)

We’ve already done some research on Power Query vs Power Automate and Dataverse vs Microsoft Studio, but as we design our dashboard formatting and build the workflows for dynamic updates, it’s important that we fully understand how all these tools and features fit together.

We also need to determine whether the upfront time and effort required to integrate these tools will deliver long‑term value by reducing ongoing updates and maintenance, allowing us to focus more on assessment. There’s a clear distinction between what’s nice to have and what’s essential. Our preference is to minimise maintenance of Dataverse tables so we can spend more time analysing our financial metrics through consolidated dashboard models. Goal is to build fully functional dashboards integrated with AI.

As advanced Excel users, our focus is on integrating AI into our existing dashboards, but backward compatibility and automation present challenges. Power Automate, Dataverse, and Studio can’t generate dashboards for visualisation, and while AI can create a dashboard‑style background image, it’s still just an image—not a functional dashboard. If that’s the case, then fully automating our financials would require Dataverse, Power Automate, and Power BI. Once the automated workflow is in place, we can then integrate Studio when building AI agents.

We’ll continue researching Power BI to confirm the best method for dynamically updating data tables between Dataverse and Power BI, assuming Dataverse becomes our primary data source. Our end goal is to use generative background images and integrate them seamlessly with our dashboard model while maintaining automated updates. The design we’re considering is:

Power Automate → Dataverse → Power BI (dashboard with Copilot background) + Studio (AI Agent)