måndag 7 december 2020

Name changes in the application we no longer know what to call.

I might have overdone the namecalling a bit now but it makes things a bit less easy. When I started working with the application it was called Microsoft Dynamics CRM which made searching for information quite easy, most of the time you just searched for "CRM <version>" and what your issue was and you got quite good results.

Sometimes I just get a bit disheartened by the application.
Today I did the first customization after the latest name change and I get to pick field type "choice" or "choices". Not much information so I turn to Google with "dynamics 365 choice choices".
That search didn't go well, or, the search did just fine but the results weren't really helping me. SO I modify it to "dynamics 365 column type choise choises" and the first hit is this page https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/types-of-fields
which tells me that I can use optionset or multiselect optionset.
I suppose "choices" is multiselect optionset, which somehow sounds a bit more intuitive than "choices".

Call me old.

Rickard Norström
Developer at CRM-Konsulterna
www.crmkonsulterna.se  

 

tisdag 3 november 2020

Read Only setting in Dynamics 365, the product formerly known as CRM

 

I had a discussion about a setting called “Read only in Unified Client” with a couple of people on the Facebook group “Microsoft Dynamics CRM” (good group if you are into the trade) a few weeks ago after Tejesh Sharma posted a blog about this setting .

The blog post is here: Make D365 CRM Entity as Read only and my comment on Facebook was “Why on earth is this even an option? Who made up this setting and what is any perceivable application?”
Now I want to be clear, the comment has NOTHING to do with Tejesh’ post which is good, the comment is why did someone actually come up with the idea in the first place.

On to the issue. Microsoft has implemented this with some update of the system. We had a customer that complained that they no longer could create products and my initial thought was that there’s some mixup with licenses and the UI app.

I wasn’t completely off, there was an issue with the app, but not in the way I originally thought. When I opened a product form it clearly said that it was read only so I went into the solution (using the classic one, I know, but it works…)



Lo and behold, the Read-only in Unified Client was set. This is nothing we’ve done, or the customer and it was present in production as well as in development. The picture is not very educational because I made it after turning it off, but it was set to true, I promise. The only entity that had this turned on was product, or at least the only entity that the customer is using so it's not turned on for everything in this case.

So if you run into an issue with customers saying they can’t edit or create objects, have a look if this setting has been turned on. If you need any help with how to do it, have a look at the blog linked above!

 By the way, there should be a symbol to use for the product formerly known as Microsoft Dynamics Customer Engagement Enterprise Edition, like Prince. In the words of the big poet Weird Al Yankovic, Never write words as numbers, unleass you're 7, or your name is Prince!

Hope this helps someone, both the text and Weird Al's lyrics.

Rickard Norström
Developer at CRM-Konsulterna
www.crmkonsulterna.se