I like this explanation very much. Alberto Ferrari is really good at describing complex topics in an entertaining way. I see a lot of potential in this feature and not just for large enterprises. I like the idea of keeping the data in the cloud and only enriching it with new data and measures. And the new concept of chaining datatasets is also very exciting. And this is probably the first time I’ve heard anyone talk about DirectQuery without making a disgusted face.
This looks like a perfect real-world scenario for me. In the last few months I have moved a lot of my personal resources to Azure. Inspired by this article I will try to build an Azure Management Tool with PowerApps
A month end procedure is a regular topic to be covered when implementing finance with D365 BC. Some finance systems throw a user into a defined routine but with D365 BC it’s much more simplistic. To remove the need for users to be experts wouldn’t a defined routine be useful?
Here is the goal: Create a Power Automate flow that will handle the month end procedure in BC with minimal user input. Principal thing here is that month end is routine so why not have something to cater for it. Caveat here being that job knowledge makes up for a big portion of this finance process so not all of it can be catered for. The scope is laid out in the next paragraph.
So what makes up a month end in BC and what is the scope of this procedure?:
Back in August I highlighted the new dataflows PowerShell script repo on GitHub. These scripts provide an accelerated starting point to working with the dataflows REST APIs and to automate common dataflows tasks. This week the dataflows team has released two new REST APIs for managing dataflows transactions (think „refresh“) and a new parameterized PowerShell […]
The idea is basically to copy the entire report (pages, filters, bookmarks,…) between two different Power BI Desktop files (.pbix).
Why this is useful? Imagine you are building a new Power BI Report and you need to reuse the entire layout from another report not only the visuals but also the layout, pages, themes, custom visuals,… Yes the dataset will be different and the report visuals will stay in an error state like this:
Yes it seems broken , but the entire layout is there and is easy to change the field of a visual to a new field of the target dataset by drag & drop a new field
To do this you just need to follow these simple steps:
Unzip the source and target PBIX files using a tool like 7zip
Second post in the „Doing Power BI the Right Way“ series. In a business intelligence solution, data must be shaped and transformed. Your data is rarely, if ever, going to be in the right format for analytic reporting. Continue reading →