AnsweredAssumed Answered

DB Level Modifications Are Not Updated By Identity Collectors

Question asked by Ece YILDIRIM on Jun 21, 2016
Latest reply on Jun 22, 2016 by Venkata Ramana Reddy Kanaparthy

Like • Show 0 Likes0
Comment • 7

Hello,

In order to test if the "Identity Collector" correctly updates the existing information on VIA, we did the following test,

- We updated the email address of an existing user directly on t_master_enterprise_users simply by following command

update t_master_enterprise_users set email_address = 'dummy' where user_id = 'USERID';

- Next, we ran identity collector.

However, we did not see correct email address having retrieved from target system and overwrote the existing information.

Are doing a wrong test? Or, is there something wrong?

Venkata Ramana Reddy Kanaparthy

Jun 22, 2016 5:07 AM

Correct Answer

Prior to 7.0, running unification should override any of the manual changes described above with the collected data. From 7.0, only the entries that differed from previous collection would be merged into master enterprise users table.

See the reply in context

No one else had this question

Outcomes

Boris Lekumovich

Jun 21, 2016 10:22 AM

Did you run unification after the collection?

Actions

Tim Willemstein @ Boris Lekumovich on Jun 22, 2016 1:35 AM

I think Boris is right, I can remember running into something simular, where we used a collected attribute as a managed attribute, the collected attribute was updated after unification.

Actions

Daniel Cinnamon

Jun 21, 2016 10:34 AM

Another comment- once a user is terminated, we no longer update any attributes for that user (sometimes we can't even- if the user is dropped from the identity feed). So I would expect your dummy value to be there still for terminated users.

Actions

Ece YILDIRIM @ Daniel Cinnamon on Jun 21, 2016 11:25 AM

Hello All,

The user is not terminated and yes, we specified to run unification after collection as in below image.

Any comments?

Actions

Edwin Mullie

Jun 21, 2016 4:39 PM

The question here is if the collector looks at that specific table, with the delta processing I wouldn't be surprised that the collector is looking at a different table. In that table the e-mail address is still the same so nothing to update.

The correct way to test is is to update the e-mail address in your source and see if that is being updated in Via after the collection

Edwin

Actions

Ece YILDIRIM @ Edwin Mullie on Jun 22, 2016 3:03 AM

Hello Edwin,

The question here is if the collector looks at that specific table, with the delta processing I wouldn't be surprised that the collector is looking at a different table. In that table the e-mail address is still the same so nothing to update.

Thanks for the comment. This is exactly what we are trying to understand. Does the collector simply ignores t_master_enterprise_users table and only considers a staging table in order to identify the changes?

Actions

Venkata Ramana Reddy Kanaparthy

Jun 22, 2016 5:07 AM

2 people found this helpful

Actions

7 Replies

Boris Lekumovich Jun 21, 2016 10:22 AM
Mark Correct
Correct Answer
Did you run unification after the collection?
Like • Show 0 Likes0
Actions
- Tim Willemstein @ Boris Lekumovich on Jun 22, 2016 1:35 AM
  Mark Correct
  Correct Answer
  I think Boris is right, I can remember running into something simular, where we used a collected attribute as a managed attribute, the collected attribute was updated after unification.
  Like • Show 0 Likes0
  Actions
Daniel Cinnamon Jun 21, 2016 10:34 AM
Mark Correct
Correct Answer
Another comment- once a user is terminated, we no longer update any attributes for that user (sometimes we can't even- if the user is dropped from the identity feed). So I would expect your dummy value to be there still for terminated users.
Like • Show 0 Likes0
Actions
- Ece YILDIRIM @ Daniel Cinnamon on Jun 21, 2016 11:25 AM
  Mark Correct
  Correct Answer
  Hello All,
  
  The user is not terminated and yes, we specified to run unification after collection as in below image.
  Any comments?
  Like • Show 0 Likes0
  Actions
Edwin Mullie Jun 21, 2016 4:39 PM
Mark Correct
Correct Answer
The question here is if the collector looks at that specific table, with the delta processing I wouldn't be surprised that the collector is looking at a different table. In that table the e-mail address is still the same so nothing to update.

The correct way to test is is to update the e-mail address in your source and see if that is being updated in Via after the collection

Edwin
Like • Show 0 Likes0
Actions
- Ece YILDIRIM @ Edwin Mullie on Jun 22, 2016 3:03 AM
  Mark Correct
  Correct Answer
  Hello Edwin,
  
  The question here is if the collector looks at that specific table, with the delta processing I wouldn't be surprised that the collector is looking at a different table. In that table the e-mail address is still the same so nothing to update.
  
  Thanks for the comment. This is exactly what we are trying to understand. Does the collector simply ignores t_master_enterprise_users table and only considers a staging table in order to identify the changes?
  Like • Show 0 Likes0
  Actions
Venkata Ramana Reddy Kanaparthy Jun 22, 2016 5:07 AM
Unmark Correct
Correct Answer
Prior to 7.0, running unification should override any of the manual changes described above with the collected data. From 7.0, only the entries that differed from previous collection would be merged into master enterprise users table.
2 people found this helpful
Like • Show 0 Likes0
Actions

DB Level Modifications Are Not Updated By Identity Collectors

Outcomes

Related Content

Recommended Content