This webcast extends the previous one and shows you how you can incorporate a signing limit approval Matrix in MS-Flow that is used for approving vendor invoices from D365FO. In addition, you can see how invoice meta data from MSDyn365FO can be sycnronized with SharePoint in order to allow users finding posted invoices quickly and easily.
This post continues my previous one and shows you how you can combine D365FO and MS-Flow workflows to send out and process MS Flow approval emails that allow the users responding to an approval request directly in the Email and view the invoice document as an email attachment.
In this webcast, I show you how you can use MS-Flow for allocating depreciation costs from the fixed asset module to the projects that you operate in the project management and accounting module. Everything works out of the box without a system modification – something that was not possible in the past.
In this post I will show you how you can inform people about newly setup ledger accounts in D365FO. Even though Alerts and MS Flow triggers are currently not available for D365FO, you can make use of the standard D365FO functionalities and MS Flow to send notifications to those who are for example responsible for setting up reports to ensure that they don’t miss newly setup ledger accounts.
This video post shows you how you can attach documents such as a dunning letters to Emails that you send out to customers. If no Email is provided a document is automatically printed and can be send by letter post. In case an invalid Email address was setup, the bouncing Emails are tracked through MS Flow and other products of the MS stack. All the things shown in the video can be achieved in the D365FO standard application in combination with products from the MS stack without making any system modification. Hope you enjoy and see you next time.
Note: If you run the latest MSDyn365FO version the Email transfer might not work in the way illustrated in the post because of a system bug. To overcome this bug, you need a hotfix installed. Details thereof can be found on LCS by searching for the issue ‘235081eMail source account setup on Electronic reporting destination setup is not stored’