CRM 2015 – Why filtered views are useful

Hosk's Dynamic Blog

If you have been a CRM developer for a length of time then you will certainly come across filtered views and they are useful and definitely something you should learn more about, particularly if you are going to be writing reports or accessing the CRM database directly.

The CRM database can be viewed and the data used but never changed directly ‚Äď Hosk

This quote means you should never change data directly on the SQL table, below are a few key reasons why
  • Direct changes to the SQL table are unsupported, this will result in Microsoft offering no or limited support if your CRM installation goes wrong. ¬†You can read more about why you should not create unsupported changes here
  • When you use the CRM SDK to change a value it could update other fields and values, direct changes to the SQL will not
  • There is no validation on the‚Ķ

View original post 1,662 more words

{Azure-CRM Integration Blog Series} Part2 – Azure Queue and Identity Provider Configuration

All about Dynamics 365, PowerApps, Power Platform and Power Apps portals by Debajit Dutta

This post is a continuation of my previous post. If you have not read the previous post, I would strongly suggest to read the same and come back here. Here is the link ‚Äď

https://debajmecrm.com/2016/05/12/blog-series-complete-in-depth-walkthrough-of-dynamics-crm-plugins-with-azure-service-bus-queues/

In this article we will understand how to configure a queue where Dynamics CRM can post messages and also configure Dynamics CRM as identity provider.

If you are familiar to Azure, normally it is just a few clicks to create a service bus namespace through the azure management portal. However with CRM, it‚Äôs a bit trick. This is because Dynamics CRM will automatically append ‚Äú-sb‚ÄĚ to the service bus namespace to identify the access control services namespace. Unfortunately with the latest version of Azure, an associated access control namespace does not get automatically created when you create a service bus. Don‚Äôt worry, you can still do that with Power shell. After all limitations sometimes help‚Ķ

View original post 526 more words

{Azure-CRM Integration Blog Series} Part1 – Understand the basics

Good one

All about Dynamics 365, PowerApps, Power Platform and Power Apps portals by Debajit Dutta

You might be thinking, we already have so many wonderful blog articles which explains how to do this. I agree. But in most of the cases, not the whole steps from the start to finish is mentioned to make it work in real life. In some cases, it is neatly depicted what you should do but why are you doing the same is missing. After all knowing the why part of it with the how part is something we always desire and helps us to design better solutions going forward.

So if you have not tried this, I hope that after reading this post you would understand things better than before. On the other hand if you have configured and the integration works for you as well but you are not sure about how it works, I would suggest you read this. If you have very good idea of what…

View original post 597 more words

{KnowHow} Set global search as default landing page for specific users in Dynamics CRM

Good One

All about Dynamics 365, PowerApps, Power Platform and Power Apps portals by Debajit Dutta

This has been a common requirement so many customers that I worked for. Setting the global search page as the default landing page for specific users. I saw a similar question today in the Microsoft Dynamics forum as well and hence I decided to pen down on how I did it.

First things first ‚Äď What is the URL for this global search page? Without this we cannot do anything. With fiddler, I just found the Url which is ‚Äď /multientityquickfind/multientityquickfind.aspx. Offcourse this is a relative url which needs to be prepended by your organization name.

Now we have the URL. But how to set it for specific users? You can create a webresource to redirect to this page and then edit the sitemap to make it the default landing page. But then it affects all the users of your system. So what is the workaround.

Well below…

View original post 235 more words

MS CRM : Sand Box Plugin – Limitations

  • Only the HTTP and HTTPS protocols are allowed.
  • Access to localhost is not permitted.
  • IP addresses cannot be used. You must use a named web address that requires DNS name resolution.(Eg: http://Your-ServerName: PortNumber /¬†SampleService.svc)
  • Anonymous authentication is supported and recommended. There is no provision for prompting the logged on user for credentials or saving those credentials

However, On- Premise CRM Servers allow registration of Plugins in None Mode rather than Sandbox mode where these limitations are overcome.

These default web access restrictions are defined in a registry key on the server that is running the Microsoft.Crm.Sandbox.HostService.exe process. The value of the registry key can be changed by the System Administrator according to business and security needs. The registry key path on the server is:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM\SandboxWorkerOutboundUriPattern

By changing this registry key value, you can change the web access for sand boxed plug-ins.

Test your WebAPI requests using Postman client

Most of the time, we do CRUD operations in DYNAMICS CRM using Plugins and Java Scripts.

How do we test the Java Script code ?

Traditional way  or ? Try Post man rest client which helps to test your API faster.

Steps to test your code Using Post man Rest Client:

1. Install Postman Rest client ‚Äď Google Chrome

2. Set Header as :

a. ¬†Content ‚Äď Type : text/xml

3. Method Name : POST

PostMan

4. Url: /api/data/v8.0/accounts

a. Example: https://******.api.crm5.dynamics.com/api/data/v8.0/accounts

5. Add you request in Body

pm_bpdy

6. Click Send Button

7. Check out the response in Headers

pm_response

Explore it .. It has many features..

Hope it helps ease your testing faster and easier !!

New Features in Solution Management in CRM 2016

It’s continuation of the previous post . If you like to read the previous post, please follow¬†Solution management in CRM 2016

CRM 2016 introduced two new features for managing and moving solutions to different environments easily.

  1. Clone a patch
  2. Clone a solution

Cloning a patch simplifies the solution updates.

If you add an entity to a solution and export the solution, the entity and all of its related assets are exported in that solution. These assets include attributes, forms, views, relationships, and visualizations, and any other assets that are packaged with the entity. Exporting all objects means that you can unintentionally modify objects on the target deployment, or carry over unintended dependencies.

To address this, you can create and publish solution patches that contain subcomponents of entities rather than publishing the entire entity and all of its assets.  The original solution and one or more related patches can be rolled up (merged) at a later time into an updated version of the solution, which then can replace the original solution in the target Microsoft Dynamics CRM organization.

How will it work along with solution ?

You can apply patches to either managed or unmanaged solutions and include only changes to entities and related entity assets. Patches do not contain any non-customized system components or relationships that it depends upon because these components already exist in the deployed-to organization. At some point in your development cycle, you can roll up all the patches into a new solution version to replace the original solution that the patches were created from.

Clone a solution Рmerges the patches with base solution and creates the new solution

Version number changes in patches and solutions

A solution’s version has the following format:major.minor.build.revision.

  1. A patch must have a higher build or revision number than the parent solution. It can’t have a higher major or minor version. For example, for a base solution version 3.1.5.7, a patch could be a version 3.1.5.8 or version 3.1.7.0, but not version 3.2.0.0.
  2. A cloned solution must have the version number greater than or equal to the version number of the base solution. For example, for a base solution version 3.1.5.7, a cloned solution could be a version 3.2.0.0, or version 3.1.5.7.
  3. In the UI, you can only set the major and minor version values for a cloned solution and the build or revision values for a patch.

If you need step by step patch creation and solution, please follow the link.

Thanks to Inogic: Create patch step by step

Keep sharing and let me know your feedbacks to improve the blog content and also to find a new dimensions in sharing the thoughts

New way of Solution management in CRM 2016

What’s new in 2016 ??

Yes so many features are new and more & more way of customization. I would like to share about changes in solutions management in CRM 2016 compared to earlier version of CRM 2015.

If we needs to work on specific entity , we will create a solution and add the entity by clicking add existing item. It will make a complete clone of the specific entity and add into your solution. But You may need to work only on specific items like forms or views or web resources or whatever.

Here’s the question why do I need to add all those If I really don‚Äôt need ?

Am so rude, I will add only what I need..  LoL..

Now its possible with 2016.

Segment the solution with the entity assets you want

Steps to create a segmented solution:

  1. Go to Settings > Solutions.
  2. Click New and create a solution. Enter information in the required fields. Click Save & Close.
  3. Open the solution you just created. In the Add Existing drop-down list, select Entity.
  4. In the Select solution components dialog box, select one or more entities you want to add to the solution. Click OK.
  5. The wizard opens. Follow the wizard to add assets for each selected entity to the solution.
  6. Click Publish for changes to take effect.

Start by choosing the Entity component.

Segmented1

Then, select the solution components.

Segmented2

Follow the wizard. In Step 1, starting in alphabetical order, select the assets for the first entity, the Account entity, as shown here.

Segmented3

Open the Fields tab and select the Account Number field.

Segmented4

As a result, the segmented solution that’s created contains Account entity. Each entity contains only the assets that were chosen.

Hope it helps !!

In Next post will see about Clone a Patch.