I posted a similar question last week about RetrieveAttributeChangeHistoryRequest and we discussed issues around permissions and the entity being auditable, but no one offered any suggestions as to why CRM might be allowing AuditDetails and not AttributeAuditDetails when the user is an admin and the entity is being audited. So, I wanted to ask a similar question and see if anyone had some ideas or suggestions. I'm getting close to wondering if there might be a bug in the current version of CRM but I am not ready to say that just yet, as it seems that something here is controlling this.
My problem is simply that RetrieveAttributeChangeHistoryRequest will return AuditDetails but will not return AttributeAuditDetails no matter what I do. It seems to me there must be more going on here that simply permissions. For example, would a custom entity that is not in a managed solution get blocked? Are their configuration settings on the entity that need to be set?
Does anyone know if the CRM SDK requires that the calling application be a service vs a winForm application? I am testing the code in a winForm application and pass my own credentials in through the connection string. I have also tested it using one of the CRM system admin accounts that we run services with and I get the same results.
If I dump the Entity Defintion I see that there are attributes such as IsVisibleInMobileClient and many others, most of which are set to false. Are there attributes on custom entities that might not allow a winForm app to view the RetrieveAttributeChangeHistoryRequest AttributeAuditDetails, but would allow AuditDetails?
Running out of ideas here to get this to work. Just seems odd that I can get AuditDetails but no AttributeAuditDetails. All of offical Microsoft pages that provide details, they all just say that you have to have the right audit level permissions, which I do as an admin, and that the entity has to be auditable, which is it. There are literally 500M audit records in the Audit table for this entity. So auditing is enabled.
So what else might block my winForm from getting access to the AttributeAuditDetails? Any thoughts?