and more in a single search tool across platforms. Read the announcement here. |
06/01/2023 04:00 AM - edited 06/06/2023 04:07 AM
We have the following situation:
We have an Organization with field "Organization Name" set to "ABC". Now we want to assign a user to that organization during import.
If we try via SAP connector in USERIMPORTJSON, it doesn't work. Value is still "ABC" and mapped to column "customer". Log says "Customer Not found for entry".
Relevant excerpt from USERTABLEMAPPING:
"USERIMPORTQRY": "SELECT DISTINCT [...] p0.ORGEH_KURZ customer,[...] FROM SAP_ZIDM_EXPORT p0",
"SAVCOLMAPPING": "[...] customer, [...]",
I can see in logs that right value "ABC" is extracted and present in "p0.ORGEH_KURZ".
I imagine that in this case you need the key instead of name and could look it up using SQL join. Is there an more direct approach to this?
UPDATE
I tried with join over customer table to set key instead of name:
"USERIMPORTQRY": "SELECT DISTINCT [...] c.customerkey customer,[...] FROM SAP_ZIDM_EXPORT p0 JOIN customer c.customername = p0.ORGEH_KURZ",
"SAVCOLMAPPING": "[...] customer, [...]",
I can see in logs that for "ABC" the right key "123" is computed. But even with the key log still says "Customer Not found for entry".
UPDATE 2
Tried developing a workaround using MODIFYUSERDATA JSON:
{
"ADDITIONALTABLES": {
"USERS": "SELECT username, CUSTOMPROPERTY2 from USERS ",
"CUSTOMER": "SELECT customername, customerkey from customer",
},
"COMPUTEDCOLUMNS": [
"customer"
],
"PREPROCESSQUERIES": [
"UPDATE NEWUSERDATA SET CUSTOMER = (select distinct customerkey from CURRENTCUSTOMER where CURRENTCUSTOMER.customername = NEWUSERDATA.CUSTOMPROPERTY2)",
],
"CUSTOMFUNCTIONS": {
}
}
CUSTOMPROPERTY2 contains customer name "ABC".
I'm getting same error message in log.
Solved! Go to Solution.
06/01/2023 06:30 AM
Hi @ASA
Can you let us know how were you tagging org to users via csv and via SAP import.
Thanks
Darshan
06/01/2023 06:34 AM
Hi Darshan,
like I said we did both. Via CSV it works, via SAP import it doesn't.
06/01/2023 06:43 AM
No thats fine, Are you using inline pro processor or the in the csv file you are mentioning the column customer, can you let me know how did you do it. ( Basically steps )
06/01/2023 06:50 AM
We use USERIMPORTJSON with USERTABLEMAPPING.
Relevant excerpt:
"USERIMPORTQRY": "SELECT DISTINCT [...] p0.ORGEH_KURZ customer,[...] FROM SAP_ZIDM_EXPORT p0",
"SAVCOLMAPPING": "[...] customer, [...]",
I can see in logs that right value "ABC" is extracted and present in "p0.ORGEH_KURZ".
06/01/2023 07:10 AM
On the user import you the column customer is key and customer name is used as org name, can you try with name column and see if you are able to import.
Also on the csv file can you let us know how if you have used inline or in csv file via column.
06/02/2023 01:26 AM
tried with "customername" instead of "customer". Seems to be ignored alltogether. I'm guessing it's not a valid colum during import.
06/06/2023 02:24 AM
06/06/2023 03:37 AM
Hi Darshan,
ticket #1634803 opened.
Also I retested import via CSV in current v23.5 and can now confirm that it also doesn't work.
06/06/2023 04:18 AM
Sure thanks
07/18/2023 02:06 AM
Solved with support team. Solution was this:
The user who is performing the import (or starting/scheduling the import job) needs access the the organizations in SAV role:
Both options are required.
07/26/2023 12:42 AM
Hello ASA!
I'm facing a similar problem at the moment. But in my case it doesn't even work with CSV import. My question is how the format in the CSV file has to be so that Saviynt sets the organization during user import. Unfortunately it's not mentioned anywhere in the documentation.
I would really appreciate your answer if you had a few minutes to help me on this problem you've already solved.
Thanks in advance and have a nice day!
Kind regards,
niklasfa
07/26/2023 04:22 AM
Hi @niklasfa
Keep the column name as customer and value as org name in the csv file and import it.
if you are importing with role_admin as well - just open the savrole and give All as access to organisation.
this should solve your issue.
Thanks
Darshan
08/03/2023 02:49 AM
Thank you, Darshan. This is working for me.