Dynamics 365 – Page 19 – Nishant Rana's Weblog

Understanding Privilege Check and Shared Access in Dataverse / Dynamics 365

Let us understand this with a simple example.

We have the following 2 custom tables having a 1 – N relationship.

Project (1-n) Artefact.

The relationship behavior is Custom with Cascade All for all the actions except Delete.

User 1 is the System Administrator and Test User 1 has the Field Service Admin role but doesn’t have any roles that give him access to the project or artefact table.

We can see the tables are not showing up for Test User 1 in the app unlike User 1 with the System Admin role.

A screenshot of a computer

Description automatically generated

Now let us assign a custom security role – Test Sharing to test user 1 that gives him Organization Level rights on the Project table.

As expected, Test user 1 now has Projects appearing in the app, and as he doesn’t have any rights on the Artefact table, he cannot see it in the form or the app.

Now user 1 shares the Project 1 record with test user 1. Remember we have set Share as Cascade All in the relationship between Project and Artefact.

But still, because the user doesn’t have any privileges on Artefact, it doesn’t appear for Test User 1 on the form as well as the app.

Now let us update the Test Sharing Role and add Read Permissions – User Level for the Artefact table.

Now Test User 1 can see the Artefacts in the related records as well as the App.

We can observe 2 things here –

Although Test User 1 only has User-level Access to the Artefact, he can still see the Artefact records created by User 1, as the parent Project record is shared with Cascade All–Share in the relationship behavior.
And as Test User 1 has only Read access he can only view the artefact records shared.

Here if we update the Test Sharing role to provide Write access at User Level, the user will be able to edit the records.

Also right now if User 1 creates the Project 2 record with the related P2 A2 artefact record, Test User 1 will only have access to the Project 2 record because of Organization Access but not to the P2 A2 artefact record as he has only has the user-level access.

Let us now update the Relationship Behaviour between Project (1-n) Artefact, and set Share to Cascade None.

Let us share the Project 2 record with Test User 1 now through the User 1 account.

As expected even after sharing the Project 2 record, Test User 1 does not have access to the P2 A2 artefact record as we had updated the relationship behavior as Cascade None for Share.

The first check that the user needs to pass is the Privilege Check, which checks if the user has the required privileges for that table before the Shared Access check

A screenshot of a screenshot of a record

Description automatically generated

Also, Check – How access to a record is determined.

Hope it helps..

Advertisements

Fixed – The latitude or longitude for the User record associated with this resource is invalid – Dynamics 365 Field Service /Dataverse

While trying to set the Start Location / End location to the Resource Address for Bookable Resource, we might get the below error

Exception Message: The latitude or longitude for the User record associated with this resource is invalid. Please provide a valid latitude and longitude and then set the start and end location for this resource again.

Here as the error message specifies we need to specify the latitude and longitude value for the corresponding resource type record associated with the Bookable Resource.

In the case of Contact, we can use the Geo Code option, and specify the address to populate the Latitude and Longitude details.

A screenshot of a computer screen

Description automatically generated

In the case of a User record we do not see the Geo Code option so there we can manually specify the values for it.

Now we will be able to update the Start / End Location as Resource Address in our Bookable Resource record, without getting any error.

Get more details on Geocoding

Hope it helps..

Advertisements

Portal does not load and displays “Server Error” or shows “Getting set up.. This might take a while” message -Portal Startup Issue (PowerApps Portal)

While trying to create a Website with Template – Partner Portal,

we observed the provisioning stuck at – Getting set up…

A white background with black text

Description automatically generated

Also, it was showing the below error on checking the Site Health.

“URL of the Dynamics 365 organization connected to this portal has been changed.” Which wasn’t the case as the URL of the organization was correct.

Usually, the 1st Web Site takes time around an hour and then any new website is provisioned within 15-20 minutes (as the common / base solutions are already installed). This was the first website for that environment, however, when it was more than 24 hours, we then raised a Microsoft Support Ticket for it.

Microsoft acknowledged this as a bug and also got the fix ready, but there was a delay in deploying it because of dependencies internally.

In parallel, they also provided us with a workaround, which fixed the issue for us.

The steps are as follows –

Create Web Site with the Customer Self-Service Portal template.
Create Web Site with the Partner Portal template.

If Customer Self-Service Portal is not needed, the website can be deleted then, followed by deleting the below Managed solutions specific to Customer Self-Service.

CustomerPortal (Dynamics 365 Portals – Customer Self-Service Portal)
MicrosoftPortalAutomate (Dynamics 365 Portals – Automate)
MicrosoftPortalEnhancedDMMigration (Dynamics 365 Portals – Enhanced DM Migration)
PortalSitewide_RPServiceApp (PortalSitewideRPServiceApp)

Also delete the website records created specific for Customer Self – Service Portal – https://www.youtube.com/watch?v=i9jeWaO93IM&ab_channel=EngineeredCode

We followed the above steps and got the Website with the Partner Portal template created successfully.

Hope it helps..

Advertisements

Using Focused view in Dynamics 365

Focused view in Dynamics 365 that allows users to view and manage all their records in one place, allowing them to be more productive, as they can stay on track and avoid getting sidetracked by switching between multiple screens to find the information they need.

We can enable and disable it for all the records from the Power Platform Admin Center

Let us select the Focused View for the Cases.

Focused View lists all the records of the view, from where we can select the record, and see its details, within the same screen.

We can search, filter, sort, select multiple records, and further customize it.

Search –

Filter –

Select multiple records and perform bulk operations –

From Settings, we can customize the appearance of it –

Here we can specify maximum 4 rows and each row can have a maximum of 3 columns added to it, it can be from the same record or the related record.

Here we have updated it as follows

Next, we have admin mode, where we can lock the customization so that users won’t be able to change it.

From the Default View settings, we can specify the tables on which we want focused view as default.

Below we can see the Focused View updated to show Case Title, Case type, Created by, and associated customer’s email address.

Get all the details here

Hope it helps..

Advertisements

Geofencing unit ‘Mile’ with id: ” cannot be removed – Dynamics 365 Field Service

While trying to delete the Unit records related to the “Distance Units of Measure for Resource and Asset Location Management” unit group, we will get the below error

Geofencing unit ‘Mile’ with id: ‘<GUID>’ cannot be removed

Below is the out of the box plugin that restricts the deletion of the unit

The code for the plugin –

UOM GUIDs –

And the GUIDs within the environment –

To know more about Geofencing.

Hope it helps..

Advertisements

Fixed – Web resource method does not exist: OnLoad error in Work Order, Work Order Service task, and other forms in Dynamics 365 Field Service

Recently we started getting the below error on the form load of the Work Order Service Task record, that also only in specific environments, and there was no changes made there.

Error Details: Event Name: onload Function Name: OnLoad Web Resource Name: msdyn_/WorkOrderServiceTask/WorkOrderServiceTask.js Solution Name: msdyn_FieldService_patch_update Publisher Name: microsoftdynamics

A screenshot of a computer error

Description automatically generated

From the error message also it was clear it was the error in the out-of-the-box javascript.

On raising the Microsoft Support Ticket, we were immediately informed that it was because of a change in the function definitions in the .js files along with its associated handlers which was done to prevent object definition collisions in the web resources.

This applied to forms of the below tables

Work Order (msdyn_workorder)
Work Order Service Task (msdyn_workorderservicetask)
Work Order Product (msdyn_workorderproduct)
Work Order Service (msdyn_workorderservice)
Knowledge Article (knowledgearticle)

And below are the changes required to be done.

Work Order (msdyn_workorder)
- Library value: msdyn_/WorkOrder/WorkOrderExperience.Library.js
  EITHER:
  - Incorrect function: onLoadLightForm
  - Correct function: WorkOrderExperience.Library.onLoadLightForm
    OR
  - Incorrect function: onLoad
  - Correct function: WorkOrderExperience.Library.onLoad

Work Order Service Task (msdyn_workorderservicetask)
- Incorrect
  - Library value: msdyn_/WorkOrderServiceTask/WorkOrderServiceTask.js
  - Function value: OnLoad
- Correct
  - Library value: msdyn_/WorkOrderServiceTask/WorkOrderServiceTaskGrid.js
  - Function value: WorkOrderServiceTaskGrid.OnLoad

Work Order Product (msdyn_workorderproduct)

Library: msdyn_/WorkOrderProduct/WorkOrderProductGrid.js
- Incorrect function: OnLoad
- Correct function: WorkOrderProductGrid.OnLoad

Work Order Service (msdyn_workorderservice)

Library: msdyn_/WorkOrderService/WorkOrderServiceGrid.js
- Incorrect function: OnLoad
- Correct function: WorkOrderServiceGrid.OnLoad

Library: msdyn_/KnowledgeArticle/KnowledgeArticleWorkOrderRelationship.js
- Incorrect function: OnSave
- Correct function: KnowledgeArticleWorkOrderRelationship.OnSave

We applied the change to the other forms also, which fixed the error for us.

Hope it helps..

Advertisements