Recently after deploying the SSIS packages, on one of the packages that uses Script Component, we started getting below error message
This happened because SSIS packages had target version SQL 2017 and the SQL Server version was 2016 (select @@VERSION)
The fix is to update the target version that matches the SQL Server Version.
Right click and go to project properties and update the Target Version to match and redeploy the project.
Hope this helps..
Recently while trying to use KingswaySoft’ s CRM Connection Manager in the Script Component we got the below error
Turned out the issue was because of the wrong version of KingswaySoft.IntegrationToolkit.DynamicsCrm assembly being referred.
C:\Windows\Microsoft.NET\assembly\GAC_MSIL\KingswaySoft.IntegrationToolkit.DynamicsCrm
Referencing the correct one fixed it.
Hope it helps..
Recently while after restoring the database while trying to import the organization we got the below error
Checking the Report Server log, 
we found the below detail
Throwing Microsoft.ReportingServices.Library.InvalidReportServerDatabaseException: , Microsoft.ReportingServices.Library.InvalidReportServerDatabaseException: The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is ‘2017’. The expected version is ‘178’.;
We can use the below commands to check the DB Version
The Database that we were restoring had the following version 178 as mentioned in the error
And in our destination server where we were had restored and imported the organization, it was 2017.
We tried out a few of the things mentioned in the forums, eventually what worked for us was to create a new Report Server database in the Destination server.
This created the database with the version expected and our import was successful.
Also, refer the below blog posts
https://www.crmviking.com/2016/02/backup-and-restore-strategies-for-crm.html
Hope it helps..
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.
CRM is a very versatile tool that’s often used for B2B sales and all its aspects, including tracking opportunities, leads, contracts, consolidating collaterals, documents and keeping contacts, tasks and events under one platform.
One of the most-overlooked essentials in B2B is the sales proposal process. But a timely CPQ, or Configure, Price, Quote software built in right on your CRM can give you that boost you’ve never had.
Thinking of adding CPQ to CRM? Consider these 7 elements to get the best system for your B2B needs.
Why Will You Need Single Sign On?
At first glance, having an SSO will mean a safer and more secure platform than without, but the biggest benefit you can take from this is complete accessibility. Sales tools must be visible and easy to get into so you and your staff can use it more. Plus, your CRM will be on the same platform as your tools, including your proposal.
In short, you’ll have the power to distribute, approve, create and collaborate on the proposal you’re working in one easy-to-use system that’s controlled by a single SSO, eliminating the need to install multiple software.
Are Templates Really That Important?
Proposals can mean the difference between landing your dream job and being stuck in your current situation. You’ll need a professional, high quality, detailed and engaging proposal or else it will get sent to where the sun doesn’t shine.
Templates can get you that stunning proposal quickly and consistently. Sales quotes won’t have to be done from scratch, thereby saving you time and effort. For business proposal templates that win deals, take a look at https://qwilr.com/templates/business-proposal-template/ and customize accordingly.
The end result? Cleaner, more professional proposals that show the client you’re really serious about your job. Automation and pre-filled templates can bring you there sooner than one without.
What About Reporting?
Sales processes are mainly made up of two parts- the sale itself and afterwards, the reporting. Metrics are there to be seen and analyzed so you can do better on your proposals the next time around. Real-time monitoring on the most important sales aspects mean you’ll be able to target areas of improvements to get better results the next time around.
When you learn how to read the data you’ll be more equipped to make the necessary adjustments for improved success. This is true of CPQ, CRM and A/B testing as well.
How Integration Can Benefit You
In the world of fast-paced B2B, the quicker you can point leads to your sales team, the greater the chances of turning a profit.
Automated proposal software integrated into your CRM platform is one of the best ways to close that gap. For example, you can use Zapier to connect to Microsoft Dynamics (on version 8 and above) and Qwilr with up to 20 unique configurations. Or, have the Microsoft Dynamics CRM tied to Qwilr easily and without having to input a single line of coding.
Here’s how the process works. Zapier connected to Qwilr supports the CRM account with automatic lead updates. Your sales team will know almost in real-time if there’s a possible lead they should follow. That said, it’s only a matter of time before your sales team becomes a well-oiled machine, nurturing proposals and getting more sales and profits.
The Role Of Support
You will need a CPQ that offers support for software development, maintenance and management. Free up all your time, concentrate on proposals and work on leads instead of having to do system troubleshooting.
Why Value and Scalability Are Important
B2B sales, mergers and growth can happen in the blink of an eye, and for that reason you will need a CPQ system that can keep pace. Moreover, while a good bargain is appealing, an invaluable partner is better for long-term success.
CRM Flexibility
Being able to spread winning bundles and create them via templates is one of the must-have features for CRMs as a whole. CPQ will make your sales team work as one even if they’re not all on the same office, area or location.
