AnsweredAssumed Answered

Duplicate Account Mapping History

Question asked by William May on May 23, 2018
Latest reply on Jun 7, 2018 by William May

Like • Show 0 Likes0
Comment • 4

Has anyone observed that anytime a collector full refresh is performed, there is a new entry added to T_Av_User_Account_History, even if it is the exact same user (which is the underlying table driving Account History view)?

I wanted to check with the community before raising a case to make sure there is not some logical reason for this behavior. It is very confusing to auditors, and I don't see any rational reason for this behavior.

It is one thing if the system requires this for operational purposes, but I see no reason for this behavior in the GUI.

Thanks,

Bill

7.0.1 P02

Russell Waliszewski

Jun 7, 2018 12:15 PM

Correct Answer

It currently is not actively being worked on by Engineering. I do believe we should be able to start this in a few weeks at which point we would then know what patch level it will be in.

See the reply in context

No one else had this question

Outcomes

Russell Waliszewski

May 25, 2018 11:16 AM

You are correct in your observation. With a Full Refresh of a collector we treat all objects and relationships (User -> Account mappings) as New. You see this in the Raw Data screen. This allows to quickly update everything in the system so that it is consistent with the Source data. The downside is that when we populate the Account History we are also adding the additional record as we think it is New.

We do have an internal ticket where we are looking at ways to remove or clarify the additional history records.

Actions

William May Jun 5, 2018 9:04 AM

Thanks Russell Waliszewski,

Do you know if the ticket is scheduled for a certain patch level?

Actions

Russell Waliszewski

@ William May on Jun 7, 2018 12:15 PM

It currently is not actively being worked on by Engineering. I do believe we should be able to start this in a few weeks at which point we would then know what patch level it will be in.

Actions

William May @ Russell Waliszewski on Jun 7, 2018 12:35 PM

Thanks for the update!

Prateek Bhatnagar - FYI

Actions

4 Replies

Russell Waliszewski May 25, 2018 11:16 AM
Mark Correct
Correct Answer
You are correct in your observation. With a Full Refresh of a collector we treat all objects and relationships (User -> Account mappings) as New. You see this in the Raw Data screen. This allows to quickly update everything in the system so that it is consistent with the Source data. The downside is that when we populate the Account History we are also adding the additional record as we think it is New.

We do have an internal ticket where we are looking at ways to remove or clarify the additional history records.
Like • Show 0 Likes0
Actions
William May Jun 5, 2018 9:04 AM
Mark Correct
Correct Answer
Thanks Russell Waliszewski,

Do you know if the ticket is scheduled for a certain patch level?
Like • Show 0 Likes0
Actions
- Russell Waliszewski @ William May on Jun 7, 2018 12:15 PM
  Unmark Correct
  Correct Answer
  It currently is not actively being worked on by Engineering. I do believe we should be able to start this in a few weeks at which point we would then know what patch level it will be in.
  Like • Show 0 Likes0
  Actions
  - William May @ Russell Waliszewski on Jun 7, 2018 12:35 PM
    Mark Correct
    Correct Answer
    Thanks for the update!
    
    Prateek Bhatnagar - FYI
    Like • Show 0 Likes0
    Actions

Duplicate Account Mapping History

Outcomes

Related Content

Recommended Content