Skip to main content


Tips for getting detailed error message from Dual Write

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. For more troubleshooting tips from Microsoft. Check out their docs page.
Recent posts

Creating SQL index via LCS

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

Find information about data entities in your system

Just bringing attention to this docs page. 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