Recently while trying to delete records we were getting the below error
It was occurring when we were selecting more than 20 records for deletion.
Turned out in the MSCRM_CONFIG database, somebody had updated the value to 20 of ExecuteMultipleMaxBatchSize column in the DeploymentProperties table
We updated it to its default value 1000 to get this fixed.
Hope it helps..
Here’s an article I wrote for @NigelFrank detailing how Dynamics 365 for Customer Service users can integrate their solution with XML. I hope you find it useful! #MSDyn365 #MsDynCRM
Integration with XML for Dynamics 365 for Customer Service users: my illustrated guide for @NigelFrank
Follow the link here
https://www.nigelfrank.com/blog/integrate-dynamics-365-for-customer-engagement-with-xml/
In my current Dynamics 365 implementation, we are back in the On-Premise world, after many years.
We thought of using the Plugin-Trace logs but was surprised to see that the Plug-Trace logs were not getting generated.
After doing the search realized that it only works for the plugin registered in the Sandbox mode.
https://docs.microsoft.com/pt-pt/powerapps/developer/common-data-service/logging-tracing
https://community.dynamics.com/crm/f/117/t/189346
So for time being, we registered in it Sandbox to get the trace.
Found the below article that has the workaround (unsupported)
http://blog.intocrm.net/how-to-write-plug-in-trace-logs-outside-the-sand-box/
Meanwhile, we can also Vote for the Idea
https://experience.dynamics.com/ideas/idea/?ideaid=abc7aceb-a8d9-e611-80c1-00155d460d59
Hope this helps..
A nice feature added to the platform ..
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/autonumber-fields
Wish they had added in the classic solution explorer as well, having 2 different interfaces only creates chaos, it reminds me of Windows 7 and Windows RT
Well this has long been awaited for. And how many times I had my customer walking up to me and ask – “I have an existing field. Do CRM provide Autonumber feature? Can I convert an existing text field to AutoNumber field?”.
Till this point my answer was Yes but with a suffix“but” in it.
However going forward you can with the new entity designer in power apps.
So you can select Primary Attribute Number field of your entity and covert it to AutoNumber type now.
Below I open the OOB Account Number field and set the Data Type from Text to AutoNumber.
Short and sweet. Isn’t it?
P.S – Only existing text fields could be converted into Auto Number Type. You can off-course create a new Auto Number Type field.
Hope this helps!
Debajit Dutta
(Dynamics MVP)
Recently created a Dynamics 365 CRM 30 days trial version (Ref: How to Setup Dynamics 365 30 days Online Trial version?) and it was navigating to CRM home page showing the list of UCI Apps, instead of showing CRM Classic Web UI.
Below is the screenshot for reference.
Later found that, the rendered URL was showing differently in the browser and having forceUCI and pagetype parameters.
https://CRMOrgName.Region.dynamics.com/main.aspx?forceUCI=1&pagetype=apps
If you want to see the old Classic Version of CRM, just use the parameter forceClassic=1, instead of forceUCI=1 and remove the parameter pagetype=apps in the URL and final URL will be like the below,
https://CRMOrgName.Region.dynamics.com/main.aspx?forceClassic=1
Bookmark the URL and explore CRM 🙂
While implementing integration packages between XML and Dynamics 365 CE, we had a requirement which required us to write a Script Component (custom code) in Data Flow task to check the status of a record in CRM and based on the value of it take appropriate action.
The initial thought was to create a user-defined variable and update the variable in the Script Component and use its value inside a new Derived Column and further in the CRM Destination Component.
However, to our surprise, although we can see the variable’s value being updated within Script Component while debugging, the same was not being reflected in the Derived Column and the Destination Component in that Data Flow task.
But within the next Script task of that Control Flow, we were getting the updated value.
Below is our sample source XML File
The package
The data flow task reads the above XML file and within Script Component it sets the value of fullname variable and we are putting its value within a Derived Column. SQL Server Destination is inserting all the values into a SQL table.
The Script Component à
The Derived Column à
The SQL Server Destination à
On running the package, the result à
It is still showing the default value.
Although we can see the value correctly updated
Now within the Script Task in the control flow, we are using a message box to show the value of that variable.
The result à
The reason for the above problem is SSIS package variables does not update during the execution of the data flow task. Those variables get updated once the Data flow task finishes. Therefore, we cannot use the updated value of the variable during the execution of a dataflow task.
Even though you could change the variable values within pre-execution or post-execution methods, it only takes effect on the value of the variable after the execution of the data flow task.
http://dineshpathirana.blogspot.com/2011/05/ssis-package-variables-cannot-update.html
So here instead of using the User Defined Variable, we used the Output column of the Script Component.
And we set the same inside the script editor.
Hope it helps.
Nishant Rana's Weblog 