Connecting CRM 2016 to Power Query in Excel 2013 with updated Odata feed

In my previous posts we had discussed about how we can connect Dynamics CRM with Power Bi and Power Query. But with the introduction of API in CRM 2016, there is slight change in the OData feed URL generated for CRM 2016.

Using the same process mentioned in older posts but making use of this new OData feed URL, we can achieve same results for CRM 2016 as well.

The url format is [Your Organization Root URL]/XRMServices/2011/OrganizationData.svc.

e.g.: https://u———–y.api.crm5.dynamics.com/XRMServices/2011/OrganizationData.svc

Advertisements

Trigger Business Rules from Business Process Flow – CRM 2016

Though we did had both Business Rules and Business Process Flow in CRM 2015 as well, but there was no way to invoke a Business Rule for some action happening on Business Process Flow. Thus if I was required to perform a simple operation of locking a case type field when case stage changes to Research, I was required to have a JavaScript instead of using a no code approach of using business rules.

But now these kind of requests can be achieved using combination of business process flow and business rule. While creating a Business Rule, we have an option under ‘Field’ to select a ‘Business Process’. This allows two kinds of checks to be performed:

  1. Check for what business process flow is being used.

  2. Check based on field stage (Active/Selected) of business process flow.

This helps in completing above mentioned scenario and similar other requirements without writing a JavaScript.

Solution Segmentation in CRM 2016: Add selected entity assets to solution

With the launch of Microsoft Dynamics CRM 2016, out of many important features added one is Solution Segmentation and Patches.

With solution segmentation we can now export solutions with selected entity assets (fields, forms, views, etc.) rather than entire entities with all the assets.

This helps a lot as previously if we were required to deploy a single new view created for an entity, we were required to deploy and publish the complete entity. This used to end up deploying some under development depended components too. The feature is most importantly useful in applying patches.

This feature allows granular control of the solution package without changing any XML. This will make ALM and Deployments much smoother.

Also by making use of the API aspect, we can try to automate build and deployment process.

Supported entity assets that can be selected for a entity are:

  1. Forms
  2. Views
  3. Charts
  4. Fields
  5. Keys
  6. Relationships (1:N, N:1, N:N)
  7. Messages
  8. Business Rules
  9. Hierarchy Settings
  10. Dashboards

Follow TechNet articles for more information on Use segmented solutions and patches to simplify solution updates