Enhance Your Workflow with Vendor Invoice Automation Dynamics 365 for Production

Vendor invoice automation dynamics 365 for Production

Now we'll see what are all the x++ extensions that we need to make. We able to receive the custom attributes that we have added on the AI builder model which is then transferred to the dataverse when OCR is done and be able to capture that information in FNO so that we can stamp it on a vendor invoice header where that utilize the same value to be translated to a vendor transaction. This is my development environment here. As extensions on FNO I have added one additional feed on vendor invoicing portable and vendors table I referenced the invoice info tables extension and the vendor invoice identity and I've also added this field for UI vended invoices to be able to reference it in the UI. Now once I've added the fields across for UI as well as for the database, I should be able to plug in the code so that I can capture it when the data is being transferred from database to a friend. So there are predefined classes against which you would need to write the extension. So if you go into the definition on this class which is vend invoice cap inv data update handler, you have four different methods which are meant for four different purposes. Invoice header is invoice register header, invoice line is invoice register line and invoice journal header is for past invoices which are landing on voice journal and similarly invoice journal line is for the past invoice. So for the demo purpose we are only using vendor invoice header entity associated one. So we're going to use update invoice header. Since it's a chain of command construct, you just need to call next. Now once you check the invoice type, you would want to get the list of all the attributes that are passed in in the call when it is actually transferring the invoice from dataverse to FNO. So those attributes are captured as a parameter. So in your chain of command you can access all those attributes you enumerate through them and then figure out what is the key value there for your property. And based on that you would want to write direction over here. So what I've done is added my MSME code here as well as I've done the select on payment terms where the payment term is number of days is only one. So whatever is a payment term which says I have to pay the following day itself and were to use that payment term to be stamped on top of the invoice header along with the due date saying header invoice date plus, that's the same way. Otherwise, if I don't find the payment terms here, I just update the due date to be next day along with populating the MSME. This is the extension I've written now for me to be able to capture what the value that is sent in on the invoice as a MSME code on the weather transaction, I just return one host inserting chain of command construction for ventrance table here I am selecting for the first required inventor invoice input table which matches the current transaction in ventrance. And if the MSME code is not blank and just updating it. So this completes all the customizations that we would need to do to bring that additional field onto finance and operations in the relevant tables.