Posts

Showing posts from September, 2018

AP Automation in Dynamics 365 Finance and Supply Chain

As a solution architect, prospects and clients often ask me for ways to improve their Accounts Payable process.  They receive hundreds of invoices every month, and it can take considerable amount of time to enter all of the detail as well as attaching the invoice for reference during the approval process.  This is an area where we have often needed to bring in an ISV solution, but that could cause other issues.  Microsoft has been doing considerable work around automation for AP and they recently released a public preview of their Invoice Capture solution. I have had the opportunity to set this up in one of my test environments so I could get an idea of what they have to offer.  As we would expect, the Invoice Capture solution is built on the Power Platform.  It uses a model driven Power App along with Power Automate Flows to integrate with Dynamics 365 Finance.  However, since it is a solution, they have done much of the work for you, including creating the standard flows to load the

Creating a date table with a fiscal year in your Power BI data model

Image
There are many different articles available on Time Intelligence in Power BI.   Many new users to Power BI do not really understand the importance of having a date table in their data model.   I have spoken on this topic on many different occasions and continue to receive a lot of questions about the topic.   In this article I am going to try and cover a few tips on how to work with dates in your Power BI model. Many new users simply use the Auto Date & Time function of Power BI.   This function automatically creates a hidden date table for each field in the model with a date or date/time data type.   This function is enabled by default and it allows for slicing by Year, Quarter, Month and Day.   The problem with Auto Date and Time is that it only works with a standard calendar (Jan to Dec).   It requires a datetime column in the fact table.   It does not work with multiple fact tables and it does not support time intelligence calculations (YTD, MTD, etc.).   So there must be