Entitlement's Audit history has an event of "Reject"

(0) Share

Report

Posted on by Community Member

Hi All,

I just happened to see the audit history of my entitlements and found something really weird.

In the screenshot provided I can find some events of "Reject" and "Activate" and found it really weird. (Microsoft Dynamics CRM 2015 - 7.0.0.3543) This seems to happen when I enter tasks into my case.

4426.001.PNG

I tested in my test environment (CRM 2016) and it has a completely different audit.

There is not activate or reject, only update.

3312.002.PNG

I appreciate any insights can could be provided.

Thanks for your time!!!

*This post is locked for comments

All responses (3)

Answers (1)

Verified answer

Community Member on at

Like (0)

Report

RE: Entitlement's Audit history has an event of "Reject"

Hi All,

Thanks for your input. My colleagues and I have checked and there are no workflows or plugins interfering with it. We ran some tests in the dev environments and everything seems fine.

It seems the behaviour is not really affecting the performance, therefore, we have decided to just let it be.

Thanks for your time,

Sincerely,

Robert.
Wayne Walton 13,728 on at

Like (0)

Report

RE: Entitlement's Audit history has an event of "Reject"

Do you have some kind of workflow or plugin that tries to set the Entitlement back into Draft for any reason? It looks like something is firing, attempting to revert the Entitlement, and CRM is rejecting action, since it's invalid.
Suggested answer

gdas 50,091 Moderator on at

Like (0)

Report

RE: Entitlement's Audit history has an event of "Reject"

Hi,

The status showing in the screenshot of 2015 environment is not entitlement status reason . Here is the status list for Entitlement in Dynamics CRM.

Value Label
0 Draft
1 Active
2 Cancelled
3 Expired
4 Waiting

I just want to know did you trigger same operation entitlement record in CRM 2016 and CRM 2015 and its having different audit history?

I would request to do the same event (Reject,Activate) in both environment and check whether the audit history is getting similar or not. This is OOB feature this should be similar considering MS did not change anything in the upgrade of CRM 2016.

Hope this helps.