Dynamics CRM

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

Posted on December 7, 2017 by Maniraj KV

Hello,

Hope everyone is doing awesome.

I believe everyone read my previous post.

If you haven’t read that, here it is Things-noticed-on-upgrading-from-v8-2-to-v9-0-part-1/

As part of upgrading, We tried importing of v8.2. solution.

Import fails:

Error 1:

In import wizard, it shows generic SQL error, try contact Administrator or Microsoft. I just downloaded the import log file and searched for error text.

Bingo!! Found something useful. Here is the error.

Entity Relationships – opportunity_parent_account – The nav pane properties for the entity relationship role a63574d6-42cc-e711-a835-000d3a1bea77 are not customizable

I felt that something wrong in this relationship. Checked out couldn’t find anything useful. While comparing the Customization.xml of this entity with previous version of the same, it sparked that there is a new set of XML tags are added to each relationship. Tried commenting that xml tags , it worked. But no idea, Why? Yet to do R&D on that.

Below xml code are commented which is part of this “<EntityRelationship Name=”opportunity_parent_account”>” tag.

Import is successfully passed this issue and got stuck in another one.

Error 2:

Process Action contains a parameter that is not supported. Name: {EntityName}, type: Entity, direction: Input

This is normal that we used to pass the entity as input. I dint feel something wrong in the input. I just deactivated the Action and imported back. Successfully imported.

In this release, i have faced these two issues. I just shared with you all.

Do share with me if you faced any issues in upgradation. I can update it to this post.

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

Dynamics 365, Dynamics CRM

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

Posted on November 25, 2017 by Maniraj KV

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.

Dynamics 365, Dynamics CRM

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

Posted on August 30, 2017 by Maniraj KV

Business Rule – Check list

Check business rule has any error. If there is any error, It will not trigger.
Check the business role scope
All the fields appearing in the business rule must be placed in th form body
Business rules will be applied to Main forms and Quick forms
If you writing multiple business rules for entity, it will trigger based on the Activation order.
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.

Dynamics 365, Dynamics CRM

Recurring Jobs Strategies for Dynamics CRM/365

Posted on August 21, 2017January 12, 2018 by Maniraj KV

Detailed post for Recurring jobs strategies

Dynamics 365, Dynamics CRM

Custom Workflow tips

Posted on April 2, 2017 by Maniraj KV

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.

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

Posted on February 13, 2017 by Maniraj KV

REAL TIME SCENARIO – MICROSOFT FLOW

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}

Posted on February 3, 2017 by Maniraj KV

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}” →

Data Migration, Dynamics 365, Dynamics CRM, SSIS

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

Posted on January 18, 2017 by Maniraj KV

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 !!

Dynamics 365, Dynamics CRM

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

Posted on December 29, 2016 by Maniraj KV

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

Data Migration, Dynamics 365, Dynamics CRM, SSIS

{User settings Id not found} – Dynamics CRM

Posted on December 23, 2016 by Maniraj KV

Recently, I faced an issue in migrating user from Non CRM application to On-Premise Dynamics CRM.

“User settings Id={00000000-0000-0000-000000000000} is not available”

I was thinking related to the user settings. Usually we don’t required to pass anything related to user settings. Then why why?? ? ? I just passed the username (domainname\username) and business unit reference to the service.

I was asking our expert goooooogle.. Wats the solution for this. None of the answer s related to me. Started revisiting my approach.. errrrrrrrrrr…

We were synced the existing Active Directory in AD configured server. I thought that while we supply domainname\username as available in AD, it will auto populate the first name and last name and other available fields. So I did not pass the values to the request.

Voila… Got it. If we were supplying the username in User creation form in CRM, it will do the auto population work. Since we were setting the values though service it will not auto populate for first name and last name. Hope you got it. Yesss we need to pass the name too..

Minimum values required for creating user in CRM are

Username as per AD
First name
Last name
Business unit reference

Hope this tip might help some body.

Keep Sharing your thoughts about this post and blog!!

” ADVANCE MERRY CHRISTMAS TO YOU AND YOUR FAMILY “