Set Properties not working when using editable grids

I found a little issue using editable grids. The following error occurs in all version since Editable Grids was introduced

When I have editable grids on the primary entity form then I cannot set the values for that entity inside a workflow. To reproduce the error do the following

1. Create a new custom entity (or use an existing entity if you dare)
2. Add a 1:N relationship from entity1 to any other entity
3. Add a sub-grid to the form of entity1
4. Go to the controls tab of the sub-grid, and choose add control. Select the Editable Grid control, and activate it for web
   
5. Save and publish the form
6. Create a new workflow for the entity
7. Add an update or create step for the record, and open the “set properties” window
8. When you select any field, the operator drop-down and field drop-down will be empty, and you cannot select any values
   

Changing the control to the standard read-only grid will prevent this error. Also, this error only occurs for custom entities with editable grids, not for default entities with editable sub grids.

Diving in to the debug console of your browser you will see the following error:

SCRIPT5009: '$P_CRM' is undefined
File: crminternalutility.js, Line: 1, Column: 1786

Browsing through the code it looks like $P_CRM should be an instance of jQuery, but it is never assigned.

Dynamics 365 Virtual Entities quick view bug

In my quest to discover all the possibilities of Dynamics 365 virtual entities I've discovered a bug that can really mess up your day.

When you've added a N:1 relationship from a normal entity to a virtual entity, and you add that field to the entity form
What I did.

1. Create new virtual entity
2. Add 1:N relationship from virtual entity to normal entity (account in my case)
3. Add the relationship field on the account form
4. Add a quick view control for the virtual entity on the account form
5. Add a reference to external virtual entity data on existing account
6. Delete data from external data source
7. Open account form
8. An error message is shown, and you cannot open the account form

The error message you get is the following

If you open the log file it states the following error type:

[Microsoft.Xrm.DataProvider.Odata.V4.Plugins: Microsoft.Xrm.DataProvider.Odata.V4.Plugins.ODataRetrievePlugin]

Yes, I'm experiencing the same thing, how can you help me?

It's an easy fix, albeit stupid one. To fix this you need to remove the quick view form (not the lookup field) from the account form, and publish the changes. Alternatively you can open the account in another form where the quick view for the virtual entity isn't present. What you'll see when you open this form is that instead of deleting the value, Dynamics will replace it with a "(No name)" reference

The reason for this is that the clever guys at Microsoft decided that they shouldn't automatically remove/delete the reference, because that would delete your references when the external system is unavailable. However, they don't have a proper check in place for quick view controls on the entity form.

I tried to put the quick view in a hidden control, hidden tab, and even collapsed section, but nothing will prevent this error from triggering. So the there is no work-around as of now.

Just gotta wait for the next iteration I guess :)

License required to install and upgrade solutions

I noticed something strange when I logged into my MSDYN365 adminstration center today with a tenant administrator.
I reset one of my sandbox instances and deployed a new July Update (v9) version, and after it completed the deployment I went in to add the O365 Group solution.

When I opened up the solutions for the instance, I got the following error message:
You do not have a Dynamics 365 license for this Dynamics 365 instance. Please get a license at portal.office.com.

I thought that this was really weird, because as an administrator you're allowed to create, export and import solutions.
I went into the instance and created a new solution, added the account entity to it. Then, when I tried to export the solution I got the following error message:
You do not have permission to access these records. Contact your Microsoft Dynamics 365 administrator.

So I went into one of my v8.2 instances and did the same operations. No issues, able to create, export and import solutions without any errors.

Went back in to the admin center and tried to manage solutions for my v8.2 instances. Got the same error message and no option to install new or upgrade existing solutions.
Surely this must be a logical slip from Microsoft, so I'm going to try and get in touch with the support team about it.

To wrap up:

• Administering solutions in the MSDYN365 Administration Center requires licensing as well as tenant or service administrator, for all instance versions.
• Exporting and importing solutions inside an MSDYN365 instance works for v8.2
• Exporting and importing solutions inside an MSDYN365 instance does not work for v9.0 (but creating and publishing does).
• Creating new items is not allowed in any version
• Publishing all customizations is allowed in all versions

Default view in subgrid resets to system default after edit

I just found a small bug (probably) when you edit the default view from a subgrid in a form. When you close the edit window (whether you made any changes or not), the default view resets to the system default.
To provoke this do the following steps:

1. Open a form editor for a form with a subgrid (or just add one).
2. Open the subgrid control, if you already use the system default then change to another one (and save)
3. Click the edit button
4. Close the edit view popup
5. The default view resets to the system default

This isn't a big thing, but if you don't pay attention you're suddenly publishing a form change into production that isn't supposed to be there, and depending on your deployment routines it could be some time before you have the opportunity to fix it.

EDIT: Also realized a much larger issue. When this happens it also resets the "selected views" (if selected). That means that selected views will reset from your selected ones to ONLY the system default view (e.g. My Activities).

Also, now you know that it isn't you who did something wrong.

Tested and verified bug since at least CRM2015, still included in the current edition.

Video of the bug in action:

Beware editing subgrid views from form designer, it switches to system default after edit at least since 2015 #MSDYN365 pic.twitter.com/9mnHgbMfHh

— Marius Agur Pedersen (@crmviking) June 7, 2017