Both fields are unique. I tried to use both one and another as a unique index at updating, but the same result.(SearchCode=Right(Name,5)&SourceID). The blocked users are created again. The information in not blocked records is corrected. I cannot overcome this situation
Are you sure there are no rules on blocked persons that might change the sourceid? Is the data exchange account not able to see the blocked items?? Can you try with a different account (System Administrator) and see if there is any difference.
Does the source data set the blocked flag? (We don't block our person records but put them into terminated status when the leave.)
Let me know how you get on and I could try and test it?
We've just updated to SP17 and we're experiencing the same problem as mentioned above. The daily import of persons is working as expected. But persons whom are blocked don't seem to be recognized and are inserted again.
Can anybody tell me what has happened with ths problem. Alexey, have you reported this to HP or did you manage to fix this?
Thanks for your reaction David. Weâ re not importing the â blockedâ attribute. Everyday we do an import in HPOVSD from another database with employees. When importing, it should be checked whether that person already exists (source id). If yes, are there any changed attributes? If no, insert that person in the database. Via value mapping the status of the employees is copied to the status of the persons in HPOVSD. A database rule will block the person with the status â inactiveâ .
But the problem starts with the fact that a blocked person doesnâ t seem to be recognized by the import mechanism. This could easily be checked by blocking a person and import that same person (with the same source id when that is defined as the primary key). Our result is that the person is inserted and therefore we end up with identical twins!
If your data exchange is nightly, you could use a SQL query to update all blocked persons to unblocked and then do the data exchange and then another sql query to turned all status=inactive persons back to blocked.
As I said - dirty but nevertheless possibly better than duplicates.