ImIronMan
Flexera
Flexera

make a combination as matching criteria to update user properties

Jump to solution
Hi Team I need to update corporate units, cost centers for 5 similar sam account names (alex1234) but coming from 5 different domains (domain1 and domain2..etc.,) . So, here user account name and the domain name combinely the unique identifier/matching criteria to update the other properties Built an adapter, added domain object, user object, and other objects as needed, and made the domain (flat name /fqdn) name and user account name both as matching criteria in order to update the same account name coming from multiple domains. However, only the first account name record is getting updated leaving other records untouched (happening only for similar account names with diff domains) Can you please suggest what config change in BAS is needed to update such duplicate account names (not actually duplicates though) with different properties depending on the domain name
0 Kudos
1 Solution

Hi Rajesh,

A unique identifier is - as the name implies - a UNIQUE identifier for an object.

If you configure your Business Adapter to use both the domain name as well as the user account name as the matching criteria, the combination of both properties is your unique identifier. After updating the first match, the business adapter will disregard the rest.

If you work in an on-prem FNMS system, your best option is to first import the data into a staging database or -table in the target environment and then use SQL for updating the target objects directly. If you work in the Cloud, you don't have that option though.

View solution in original post

2 Replies
ImIronMan
Flexera
Flexera

Hi All

Just following up on this question. Can someone please respond

0 Kudos

Hi Rajesh,

A unique identifier is - as the name implies - a UNIQUE identifier for an object.

If you configure your Business Adapter to use both the domain name as well as the user account name as the matching criteria, the combination of both properties is your unique identifier. After updating the first match, the business adapter will disregard the rest.

If you work in an on-prem FNMS system, your best option is to first import the data into a staging database or -table in the target environment and then use SQL for updating the target objects directly. If you work in the Cloud, you don't have that option though.

View solution in original post