Monthly Archives: January 2019

What the heck is a reference panel?!

(Update) this seems to be old news because of this older post:    No navigation icons on the screenshots there, though.. hm..


While looking at the Health Care Accelerator solution earlier today, I noticed this strange navigation panel on the right:


Have never seen it before, so I tried clicking some of those items. Lo and behold, they are perfectly clickable:


So, I went to the designer.. That part of the form looked like a regular section with grids:


But was it? Unlike your other sections, this one is somewhat unique:


I can’t change the name, and I can’t even set some of of the regular properties. Hm..

Can I re-create a similar section somewhere else? Turned out I can, though I am not sure how supported it is.

Here is how to do it – you’ll probably have to mess with customizations.xml, so I’m assuming you know how to work with it:

  • Create a new solution
  • Add your entity
  • Add a form you want to update
  • Make sure you only have subgrid controls on the form you want to update (remove all other input controls)
  • Make sure you are using a one-column section
  • Export your solution and extract the contents
  • Open customizations.xml
  • Find the section and add ref_pan_ prefix to the section name
  • Within that section, replace classid attribute of all subgrid controls with this id: “02D4264B-47E2-4B4C-AA95-F439F3F4D458”


Save the file, re-package your solution, and see what happens. For example, in my case I got this kind of navigation for the recent cases/recent opportunities/entitlements:


What does it all have to do with the “reference panel”? This is how those sections are called, it seems. For example, if you don’t replace subgrid control id above, you’ll get an error that will be explaining that only some specific controls can be used in the reference panels etc.

PS. You probably noticed that I did not get the icons right above.. Not sure why yet, may need to get back to it.


Dynamics login errors

I see the error below relatively often, since it’s not extremely unusual to see a user that was created without giving that user any roles in Dynamics (or, maybe, that user was moved to another business unit and lost his/her roles in the process):


The error is absolutely clear – we just need to assign roles to the user.

What turned out to be quite a bit more confusing is the HTTP 404 error I saw this morning when trying to access Dynamics under one of the test accounts:


“No webpage was found for the we address: https://…

Well, of course there was a webpage since I was able to open that page under my regular user account. How come?!

The problem turned out to be with the business unit of that test user account. The user account had all the roles, it was an active account in Dynamics, so, when looking at the user account, everything looked perfectly fine.

The business unit, however, was disabled. I am not sure why it was disabled (guess that’s what test accounts are for.. somebody was testing something), but the end result is: you can see this error message if your user account is linked to an inactive business unit in Dynamics 

What’s wrong with those security roles?

You know how security roles in Dynamics are duplicated for each business units, right? So you have a role in the root BU, and there is a copy of that role in each of the child business units.

So what would you be thinking if there were a role in the root business unit for which there would be no corresponding role in the child business unit?

For example, on the screenshot below, you can see how all other roles are displayed in pairs (one per business unit); however, those highlighted roles are unique:


It all becomes clear once “parent role” column is added to the view:


Somehow, my “Test Role” in the child business unit has a parent role that’s named differently. There is an easy fix – I just have to update parent role name (flip it back and forth) – everything gets synched after that:


So how come?

Turned out this is something that may happen during solution import – in my case, the role was originally imported through a managed solution. Then it was updated in the source and re-imported again. Somehow, once the role was imported, the display name of that role got updated only in the root business unit.

Technically, nothing gets broken when this happens. But, of course, it the role name is mentioned in some kind of user setup instructions, those instructions become rather confusing.

PS. And, btw, the credit for figuring out most of this(well, to be fair for creating the issue, tooSmile ) goes to Richard Lund from MNP.