Posted in Dynamics 365, Dynamics Portal

{Set Two Optionset value in Dynamics Portal}

Dear All,

It’s been a while i haven’t write any post. Quite busy with office stuffs.

Currently busy working in Dynamics Portals and Dynamics 365 v9.0 with updated client API.

Here I would like to share quick tip on setting field values on Dynamics Portal. We know that lot of articles are flown in the google for get/set values. we cant find for Two options set fields in Dynamics 365/CRM.

Here is the snippet which works for it.

Two option set field is rendered as group radio button.

Hope this tip will help to save your time.

If you have any alternative approach, Please do share with me.

If you need a help, you can reach me at any time.

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

Bug fixes & Release

One of the day to day activities of developers is bug fixing and its releases to different environments.

When there is no version controller,no package deployment, How do we track the fixes in solutions.

Definitely we will work on lot of bugs. So keep track on the bugs which you are working.

How do we track then? Make an excel sheet, track the changes in a column, what are all items need to move for fixes and its releases.

Do you think it is easy to track like this. When multiple developers are working on bug fixing. How do we merge? How do we prepare the deployment package?

OmG! There is a chance for missing lot of things or overwrite on other’s work or latest changes are not moved.

Use version controller and package deployment model. Keep spoc for all deployment activities.

How do we manage solutions?

  1. Solution patching in Dynamics CRM
  2. Keep all the changes in patch
  3. It helps to keep the all the developers change at their own patch. Finally can merge.
  4. Easy to deploy

Lot of ways to manage your solutions, bug fixes, hot fixes.

Finalize the way, make the developers to follow the strategy to keep up their work and track their fixes accordingly.

It helps in many ways to reduce the re-work time..

Might be a small tip, but keeping routine which helps to use our resources time efficiently.

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