Logic during ACCOUNTS_IMPORT_JSON on WORKDAY_SOAP connector?

[Community_User]

Originally posted on May 15 2020 at 18:08 UTC

Can I utilize logic operations during account import mapping? I want to utilize a single account.customproperty and map to the entity type in Workday.

For example:

if exists(Worker_Data.Employment_Data.Worker_Job_Data.Position_Data.Worker_Type_Reference.Employee_Type_ID) then "Employee"

elseif exists(Worker_Data.Employment_Data.Worker_Job_Data.Position_Data.Worker_Type_Reference.Contingent_Worker_Type_ID) then "Contingent Worker"

etc..

[Community_User · Accepted solution]

Originally posted on May 15 2020 at 20:33 UTC

Answered my own question. On a SOAP connector account import, you can specify logic in a TEMPMAPPING field.

So I impoprt the foundational decision data into CP7 and CP8, then use a TEMPMAPPING to define CP9.

"TEMPMAPPING1" : [ "CUSTOMPROPERTY7 = 'Employee' where customproperty8 IS NOT NULL and customproperty9 IS NULL", "CUSTOMPROPERTY7 = 'Contingent Worker' where customproperty9 IS NOT NULL and customproperty8 IS NULL"]

}

[Community_User]

Originally posted on April 6 2021 at 07:56 UTC

Hi Ken,

Can you provide some sample JSONs for create account and import account?

Regards,

Yashpal

[Community_User]

Originally posted on April 6 2021 at 12:58 UTC

I only have Workday v1 connector json. Do you want that?

[Community_User]

Originally posted on April 6 2021 at 13:18 UTC

Yes, Ken, Can you please share that?

[Community_User]

Originally posted on April 22 2021 at 04:11 UTC

Hi Ken,

Can you please share the connector json?