Dynamics NAVAX

 There is a new feature for Financial tags on Sales orders. https://learn.microsoft.com/en-us/dynamics365/finance/general-ledger/financial-tag This feature can be enabled under the feature management. After it is enabled, the sales order form will show a new fast tab under the header and line. It is similar to the financial dimensions but shows as a grid. Note that the tags do not show under the posted invoice journal but the field FinTag is stamped. If you want analyse or do reports, it is possible. The great thing about this feature is that it carries over to the voucher transactions.  Below are 2 examples I posted. First example, I created a sales order with 2 lines and unique financial dimensions. The system splits the vouchers by financial dimension and hence the tags appear correct. On a second example, I created a sales order with 2 lines but have the same financial dimension on them. The product sales voucher line has only the first sales order line tag. 

Microsoft recently released the new Invoice Capture for Dynamics 365 Finance. I ran through installing and configuring it.  From that experience, below is my brain dump and hopefully it can help with things that are not so obvious. Three type of invoice captures There are three invoice type paths that can be captured. These drive the screen layout and what kind of information is mandatory. PO invoice Header-only Cost invoice When an invoice comes in, you can select one of the three invoice types. Below are the three screen layouts and differences. PO invoice – Invoices of this type are associated with purchase orders. The purchase order details must be determined on each invoice line. Both the header and the lines must be reviewed in Invoice capture. This will create a pending vendor invoice. Header-only – Invoices of this type are associated with purchase orders. The purchase order field on the invoice header is a mandatory field. If the Automatically create invoice lines featur...

In some cases Dual Write gives you some cryptic error messages. Here are a couple of tips to get or find the errors. Tip 1. If you get an error while mapping or trying to set up a new map. You can get a bit more info from using browser developer tools. In Chrome, just right click and select Inspect. Click on Network and start recording (trace). Hopefully you get a bit more detail with the error. Tip 2 If you are getting an integration error. There is a table that stores all the errors. https://XXXaos.cloudax.dynamics.com/?mi=SysTableBrowser&tableName=DualWriteErrorLog For more troubleshooting tips from Microsoft. Check out their docs page. https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/dual-write/dual-write-troubleshooting

LCS has some really great tools for checking performance. Its really a matter of trying to get used to them and knowing whats available. Under the Environment monitoring > SQL insights > Performance metrics. You can find some slow queries and how they are affecting the environment over time. I found that SalesLine table was missing an index for Revenue recognition. Warning: Do this at your own risk. You could break the system if you haven't tested this properly. I raised a support ticket but was asked to create a non-unique index on the table via LCS. Go to Environment monitoring > SQL Insights > Actions Select "Create non-unique index on a table". Turn of the "Allow page locks". Talking about that risk. I got an error after I did the above with batch jobs. I had to restart the batch service in LCS to fix the problem. This is the error I got with batch job to post the sales invoices.  Refer to Microsoft Docs page on this. Typically you want to do th...

Just bringing attention to this docs page. https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/data-entities-report I only saw it today and it has some nice scripts that you can run to generate information. Go to the  github  project it references and run the scripts. Script Outputs AggregateDataEntitiesReport.ps1 AggregateDataEntities.csv AggregateMeasuresReport.ps1 AggregateMeasures.csv DataEntityFieldReport.ps1 DataEntityFields.csv DataEntityReport.ps1 DataEntities.csv KPIReport.ps1 KPIs.csv LicenseCode-ConfigKeyReport.ps1 LicenseCodes.csv ConfigKeys.csv ConfigKeyGroups.csv MenuItems.csv SSRSReport.ps1 SSRSReports.csv TablesReport.ps1 Tables.csv This report takes awhile to run, but it produces output as it runs. WorkflowTypesReport.ps1 WorkflowTypes.csv The scripts use C:/, you will have to change to K:/ or where ever your application is sitting in. I just did a text replace "C:/" with "K:/". It will export your files under the users...

In the recent updates of Dual Write, Microsoft released a pricing and inventory on hand integration in CE. Real time pricing calculation and inventory on hand as per FinOps business logic. In this post, I wanted to cover how it seems to magically work. As you know by now, Dual Write uses a push architecture. Where either FinOps pushes to CE or CE pushes to FinOps. Both call a web service on the other side to sync data. Any errors that occur are presented to the user in real time. However, the pricing and inventory on-hand feature is different. These two features pull limited calculated data as needed. Watch the " Prospect to cash in dual write " tech talk from Microsoft and you will see why.  You wouldn't want to integrate (replicate) inventory levels or pricing logic in CE. The reason this is done this way is because integrating this kind of data would cause performance problems or a lot of chattiness. So, what Microsoft has done is a pull the data as needed (pull archit...