Customer experience | Sales, Customer Insights,...

Microsoft.Dynamics.Service.Plugins Calling User is Disabled

(0) Share

Report

Posted on by Nazeer Allahham

Hi all,

When trying to create a new Case, I am receiving the following error:

The user with SystemUserId=xxxx in OrganizationContext=xxxx is disabled.
The plugin causing the error is 'Microsoft.Dynamics.Service.Plugins.PostOperationIncidentCreateEntitlement'.

So we have disabled that user, but from where I can control the calling user for Microsoft.Dynamics.Service.Plugins.PostOperationIncidentCreateEntitlement.
When trying to browse list of assemblies from Plugin Registration Tool, I cannot find Microsoft.Dynamics.Service.Plugins there.

I need to know how to change the calling user or team for Microsoft.Dynamics.Service.Plugins to fix the problem.

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Pradeep Rai 5,489 Moderator on at

Like (0)

Report

Hi,

Above assembly is OOB and we do not have control over it.

I would suggest first check the owner of case record. It should be active user and After this, check do you have any workflow running on create of case entity.

Because Additional custom business logic will be the key issue here.

You have to find that.

Was this reply helpful? Yes No
Suggested answer

Abdul Wahab 12,119 Moderator on at

Like (0)

Report
Hi Nazeer Allahham,

How about if you check the workflows and plugins against the case table? As per the error, it seems the plugin. To see details follow the instructions:

Plugin:

Open the plugin Registration tool

Change the view to Display by Entity. I think now you can find that step

Workflow

Make.powerapps.com.

Correct environment.

Advance settings

Processes

View: All Processes

Add filter on Primary Entity to Case

Details

Was this reply helpful? Yes No
Nazeer Allahham 10 on at

Like (0)

Report

Thank you Abdul Wahab for your reply.

But before asking this question, I have went through all of the above mentioned steps.

I came up with that the reason is one of the following:

- The ownership of the case is changing on creation and before entering to the plugin causing error.

- The calling user in the plugin is configured in way leading to throwing the error.

So, do you have any idea or a helpful resource, that I can decide which the proper cause.

Was this reply helpful? Yes No
Suggested answer

Abdul Wahab 12,119 Moderator on at

Like (0)

Report
Hi Nazeer Allahham,

First, It is important to check the plugin step calling the user

Determine the component who is responsible for that owner change.

Was this reply helpful? Yes No
Community member 2 on at

Like (0)

Report

Please check your SLA record ownership, is that disabled user owns any SLA record?. Because whenever case record created which is applicable to a SLA. CRM will try to create entitlement record and assigned to the owner of the SLA.

Was this reply helpful? Yes No