Posted in Dynamics 365, Dynamics CRM

Things noticed on upgrading from v8.2 to v9.0 – Part 1

All,

Hope everyone doing great. It’s been a while. Pretty much busy in travels and new learnings.

Recently, we got requirement to upgrade from Dynamics 365 online v8.2. To v9.0 and client is using Dynamics 365 Native Mobile App heavily.

Most of them aware that few client side scripting Syntax are deprecated in v9.0.

How it will Impact if we migrate to v9.0.??

As we all know that we have typical form and Interactive form. We used to access the Interactive forms only through the interactive service hub url.

What’s the headache for the developers was need to design twice in earlier versions.

Now it’s changed in v9.0. Design once, Access traditional way or New Unified Interface aka Interactive Service Form.

As per Microsoft, new Unified Interface loads faster than the traditional one. We all know that Mobile App loads slower or takes time whenever login. It’s resolved in v9.0.

v9.0: Mobile App loads only the Unified Interface Sitemaps

Then how to define the Sitemaps as Unified Interface??

Yes, It has a property to switch between Web (traditional ) and Unified Interface.

One bottleneck in using Unified Interface is deprecated Syntax should be changed. Otherwise it will not work.

So make sure that all your client side scripts are using newer Syntax if you wish to utilize the Unified Interface feature. Otherwise it will work as usual in Web (Traditional ) after the upgrade also. But it will not work in Mobile App. As I mentioned above, Mobile app relies on Unified Interface.

If you have lot of custom ribbon buttons, that may be visible in unified interface or may not. So need to check your code and display rules.

We faced some difficulties in importing solutions to v9.0. I will keep you posted on new issues and errors on upgrade.

Highlights:

  • Native Dynamics 365 Mobile App relies on Unified Interface.
  • Unified Interface don’t like deprecated client side Syntaxes. So identify and change it before the upgrade.
  • I felt Unified Interface is not showing client side scripting errors as friendly as compared to traditional form. May be I need to see deeper.

Still we haven’t completed the upgrade. We need to update the deprecated syntaxes. Then only we can complete the activity. I will post on those.

Am writing this post through mobile. Kindly bear me, couldn’t share screenshot.

Feel free to reach out to me if you need any help on upgrade your project / consulting.

See you all in next detailed post.

Posted in Dynamics 365, Dynamics CRM

Dynamics CRM/365: Business rule not working, here is the checklist

Business Rule – Check list

  1. Check business rule has any error. If there is any error, It will not trigger.
  2. Check the business role scope
  3. All the fields appearing in the business rule must be placed in th form body
  4. Business rules will be applied to Main forms and Quick forms
  5. If you writing multiple business rules for entity, it will trigger based on the Activation order.
  6. If the scope of business rule is not on entity, it will trigger only on client side.

If you have any tips, please share me in comments.

Posted in Dynamics 365, Dynamics CRM

Custom Workflow tips

Good Morning !! 
Hope everyone doing awesome. 

Would like to share this tip with you all.

I believe everyone knows how to debug custom Workflows using Plugin Registration tool. 

Trick is that while trying to profile, you will not be able to find steps for that respective workflow assembly. 

Check: Whether you have used this assembly in workflow ?

Most of the time, we would have used in workflow. if it’s not working only, we used to come for  debugging.:-;

No ? Start using it ..Then only steps will be visible in Plugin Registration tool.

Still steps are not visible n PR tool.

Yes ? Check whether you used this Custom Workflow assembly in conditional approach. If so, it will not be visible. So workaround will be use straight way in work flow.debug it. Fix your code. 

Hope this tip will help to save your time in analysing it. If you have Better way, please do share me. 

Thanks for reading and keep sharing. Happy Blogging.

Posted in Dynamics 365, Dynamics CRM, Microsoft Flow

{No code approach} Delete attachments from corresponding SharePoint folder when a record is deleted in CRM using Microsoft Flows

REAL TIME SCENARIO – MICROSOFT FLOW

Debajit's Dynamic CRM Blog

Off late, I have been working with Microsoft flow and boy! I am liking it. It is cool and specially considering the fact that it simplifies whole lot of stuffs that you would normally require to write lot of code, make it even more appealing.

So here I was with a requirement.

There was OOB CRM-SharePoint integration enabled and the client wanted that whenever an entity record is deleted from CRM, the documents in the corresponding SharePoint folder should be deleted as well.

Now the OOB behavior does not support that. Even if you delete the record, the folder corresponding to that is present in the SharePoint path with all the documents.

So what are my options here. Well some custom code that would run when the record is deleted in CRM and that code would be responsible for deleting the documents from the SP Folder. On top of that…

View original post 942 more words

Posted in Data Migration, Dynamics 365, Dynamics CRM, SSIS

SSIS – {The column cannot be processed because more than one code page (1256 and 1252) are specified for it}

Second post in 2017.. hoping for more posts in upcoming days.

Recently, I faced this issue while migrating records from Source database to Staging database.

Package background: I have developed the package in development server and deployed in migration server.

Analysis: I just checked the code page of the error column in dev server. It’s 1252. Was thinking how come 1256 ? .

1951885
Continue reading “SSIS – {The column cannot be processed because more than one code page (1256 and 1252) are specified for it}”

Posted in Data Migration, Dynamics 365, Dynamics CRM, SSIS

{SSIS – Special characters getting appended while migrating records from CSV to SQL table}

After long back..

Hope everyone had wonderful New year and Pongal celebrations. Hoping for the next year (2018)  Pongal celebrations  with full fledged government support  for conducting JALLIKATTU in Tamil Nadu.

Lets discuss an important tip for data migration.

Recently I faced an issue in moving records from CSV file to Dynamics CRM 2016.

Scenario:  In my data file, it has Arabic letters. So i set the properties of CSV file in UTF-8 format. After i moved the data to the table, checked out the Arabic field column. It has some special characters are appended. If i am moving using Excel file, it’s not appending any special characters.

Resolution: After searched various forums , I have found that It’s a data type issue. If we check the arabic values column and its data type, it shows as DT_STR. But it supposed to be DT_WSTR. So changing the data type of the required columns to DT_WSTR data type will help to overcome this issue.

Hope will help somebody in future.

Happy sharing !!

Posted in Dynamics 365, Dynamics CRM

Under the Hood – There’s a Dynamics 365 App for that

Excellent post.. Deep Insights about Dynamics CRM evolution
#Dyn365 #NewFeatures

Dynamics 365 Northern Ireland

Microsoft has surely been looking at Salesforce for the past few years, feeling somewhat envious of their ‘apps’ market. If you take Salesforce at their word, they have over 1.4 million registered developers, so the apps market for Salesforce is clearly not a flash in the plan.

With the recent launch of Dynamics 365, there appears to be a concerted effort at Redmond to build an ecosystem around Dynamics 365, but how has this been implemented and what do application developers need to know?

365 Apps v Solutions

Back in the day when solutions were introduced in Dynamics CRM 2011, you could see the start of an effort by Microsoft to have proper application lifecycle management around Dynamics CRM customisations and configurations.

solutions CRM 2011 Solutions

Unmanaged solutions were a way a developer could keep track of their many bits and pieces within CRM. Managed solutions were way of packaging…

View original post 1,198 more words

Posted in Data Migration, Dynamics CRM, SSIS

{Integration Services Deployment wizard – AppCrash}

Hello Everyone,

Hope everyone doing good and preparing for long vacation 😉  Advance Merry Christmas and New year wishes to all.

Let’s discuss one of the issue faced in data migration… 

Earlier i faced an issue in deploying my SSIS package and shared the experience and how to overcome that in the below link.

Unable to create the type with the name ‘CRM’ (Microsoft.SqlServer.ManagedDTS)

Today I faced an another issue while deploying my packages in Pre-Production server. It’s something strange and new to me.

“isdeploymentwizard.exe is Crashes every time and unable to deploy the project” 

I have checked everything that’s used in the packages like

  • Third Party component installed properly or not
  • Changing Project to run in 32 bit or 64 bit run time
  • I have used BDD also. I have checked that whether BDD is installed or not

Still I faced the same issue. Then i checked the event viewer and found something useful.

Faulting application name: isdeploymentwizard.exe, version: 12.0.2000.8, time stamp: 0x5306c9c6

Faulting module name: dts.DLL, version: 2014.120.2000.8, time stamp: 0x5306c90b

Exception code: 0xc0000005

Fault offset: 0x0006f806

Faulting process id: 0x198

Faulting application start time: 0x01d25c4e8748942d

Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\isdeploymentwizard.exe

Faulting module path: C:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\dts.DLL

Report Id: 2f82e5ec-c842-11e6-80ca-005056af2141

Faulting package full name:

Faulting package-relative application ID:  

Highlighted line remind me that I have used SQL connections in my package. So possibly something related to SQL versions. Then I checked that SQL version which was used for developed are “SQL server 12.0.5203″. But the deployed SQL version is SQL server 12.0.2000“. It is lower than the developed version. To verify that just replaced the “dts.Dll” of higher version in deployed SQL server. Now am able to deploy it.

“So make sure that while deploying in different server, SQL version should be same as developed version.”

Do share your thoughts!! Keep Sharing !!