Hi,
I have use case where I have a HR system in ISC with some data including CostCenter and a downstream JDBC source with the data of 6 attributes that are not coming through HR, but have to be visible on the Identity cube whose cost center matches the cost center from HDBC source. , only common attribute between the HR and JDBC source is the Cost Center attribute. The Cost Center is the Unique Identifier on JDBC as the source has only Cost Centers as the accounts in ISC.
Now I want to use the Cost Center attribute and design transforms for those 6 attributes through which it should out put the respective 6 attributes when it matches the Cost Center.
I tried something similar as below, but I am seeing error.
In the below Transform keyAttribute is the attribute that exists on JDBC source and valueAttribute should be the output value of the attribute that is needed from the transform,(which is one of the 6 attributes).
{
"type": "reference",
"attributes": {
"sourceName": "JDBC Source",
"keyAttribute": "cost_center",
"valueAttribute": "Business_Area_Code",
"input": {
"type": "identityAttribute",
"name": "costCenter"
}
}
}
Error: transform id must not be null.
Please let me know if you have any inputs that can help!
Thank you in advance!
This is a weird way to go about it, but I don’t see a more straightforward way and it’s in line with what you’re trying to do. You could set up an Identity Profile that creates identities for your cost center records, then use a “Get Reference Identity Attribute” transform to pull the values. it would look like:
{
"attributes": {
"name": "Cloud Services Deployment Utility",
"operation": "getReferenceIdentityAttribute",
"uid": {
"type":"accountAttribute",
"attributes":{
"attributeName":"cost_center",
"sourceName":"Your HR source here"
}
},
"attributeName": "businessAreaCode"
},
"type": "rule",
"name": "Get Reference Identity Attribute Transform"
}
You may want to consider the potential license impact of adding these identities before you actually go this path.
Thank you @KevinHarrington for your prompt response. I would like to clarify that currently all the accounts(Cost Centers) in the JDBC source are un-correlated, and if possible, we would like it to stay uncorrelated and avoid creating an Identity Profile.
So considering above scenario, is it possible to compare the Cost Centers of the accounts from the HR system to the Cost Centers of the JDBC source and display the respective attributes from the JDBC source in a transform? In other words just like a Look up in excel comparing two columns and displaying the column next to it when the criteria matches.!
There is no transform type that allows querying accounts that aren’t correlated. I have actually done something like this before though, now that I think of it. I created a script to query the HR system and dynamically rebuild a lookup transform periodically via an API call.
HCMLocationLookup.ps1 (2.7 KB)