Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Microsoft Dynamics 365 - Auditdetails

Not planned
Gu Xie User

Context:

Microsoft Dynamics 365's connector supports the Audit entity, which outputs the high level entity CRUD operation tracking.

However, it does not pull down the Attribute level audit history on a per entity basis.
This is known as the auditdetail portion of the Audit API and it returns information about what changed on audited fields in CRM - eg. Address, Email, Name, etc.

Value for Customer:

Auditdetail History is one of the largest volume storage for Microsoft Dynamics 365 customers. It takes up the bulk of data storage volume and Microsoft charges quite a lot for extra storage.

If Fivetran extracts the Auditdetail History, then Snowflake will serve as a warm data store for Auditdetails and thus allowing the purging of extra Audit History in Dynamics 365 and having significant cost savings.

At the same time, the attribute level audit history allows analytics to identify anomalous patterns of data integrations to our CRM system, which is integrated to many different applications.

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Sadie Martin Fivetranner
    • Edited

    Hi all,

    Sadie from the Product team here. The attribute level audit detail data is already synced as part of the connector in the AUDIT.CHANGEDATA column. However, we recognize that this data may not be easy to use because it is a string that contains all the attributes whose IsAuditEnabled property is True and are being changed (Microsoft docs here). Are you interested in having the data in this column split out into a separate table that is more user-friendly? More details will help us prioritize building a solution.

    Best,

    Sadie

  • Ray User

    Hi Gu Xie

     

    Thanks for the detailed request! It sounds like there is indeed a lot of value to replicating this data. To confirm, is this page describing the same Attribute-level audit history you're interested in? 

    We don't have any current plans to support this, but we'll gladly add it to our backlog. We'll continue to monitor for demand including comments and upvotes on this thread!

    All the best,

    Ray Harris
    Product Manager, Sales & Customer Success Analytics

  • Gu Xie User

    Hi Ray,

    That is correct. The page details about the Audit trail that CRM stores.

    I have built this sync pipeline in the past and the data structures are attached.

    Audit: High level audit that is already ingested via Fivetran via the Audit Entity API.

    • This only stores at the object level audit indicating that fields xyx have changed on a Contact record for example. Or a new Contact record was created / deleted.

    AuditDetail: Attribute level definition that is an extension of the Audit entry above.

    • Has an AuditId to refer to the Audit high level entry. Eg. Contact was updated.
    • Has FieldName, OldValue and NewValue to indicate what was changed
    • This is known as the Audited Data Changes in the MSDN doc