Leveraging Intelligent Recommendations for Operational Transformation. AMS Partners click HERE | EMEA/APJ Partners click HERE |
11/29/2023 06:25 AM
We have an endpoint where the account name will be same as users customproperty1 or customproperty2
i have added the following as the user correlation rule on the endpoint.
upper(trim(users.customproperty1))=upper(trim(accounts.name))#
upper(trim(users.customproperty2))=upper(trim(accounts.name))#
upper(trim(USERS.CUSTOMPROPERTY59))=upper(trim(ACCOUNTS.NAME))#
upper(trim(USERS.CUSTOMPROPERTY60))=upper(trim(ACCOUNTS.NAME))#
upper(trim(USERS.CUSTOMPROPERTY61))=upper(trim(ACCOUNTS.NAME))#
upper(trim(USERS.CUSTOMPROPERTY62))=upper(trim(ACCOUNTS.NAME))#
upper(trim(USERS.CUSTOMPROPERTY63))=upper(trim(ACCOUNTS.NAME))#
upper(trim(USERS.CUSTOMPROPERTY64))=upper(trim(ACCOUNTS.NAME))#
upper(trim(USERS.CUSTOMPROPERTY65))=upper(trim(ACCOUNTS.NAME))
this is in version 23.4.
and also on the side note is it possible to restrict user to only one account for this endpoint and not allow him to request for second account.
Solved! Go to Solution.
11/29/2023 06:41 AM
@VamsheeVazza If users customproperty1 or customproperty2 is same as account name then you can try basic config in user account correlation rule.
Could you please share the sample data for single user
11/29/2023 08:07 AM
lets take me as a user
i have my customproperty1 as ei1234
and there is an account with account name ei1234
this account should correlate to mu user profile.
i have the above correlation rule in the endpoint. but the account is not mapped to my user profile and account is not showing up in y accounts under my user profile.
11/29/2023 08:30 AM
@VamsheeVazza Did you run the account import job after correlation rule configured in the endpoint?
If this reply answered your question, please accept it as a solution and kudos.
11/29/2023 08:44 AM
yes we did run the import job.
11/29/2023 07:03 PM
try below and share logs after import job
upper(trim(users.customproperty1))=upper(trim(accounts.name))#upper(trim(users.customproperty2))=upper(trim(accounts.name))#upper(trim(users.customproperty59))=upper(trim(accounts.name))#upper(trim(users.customproperty60))=upper(trim(accounts.name))#upper(trim(users.customproperty61))=upper(trim(accounts.name))#upper(trim(users.customproperty62))=upper(trim(accounts.name))#upper(trim(users.customproperty63))=upper(trim(accounts.name))#upper(trim(users.customproperty64))=upper(trim(accounts.name))#upper(trim(users.customproperty65))=upper(trim(accounts.name))
12/07/2023 08:23 AM
It didn't fix the issue.
trying the basic config worked instead of advanced query.
turns out Upper and Trim are not working in correlation rule
12/07/2023 09:03 AM
@VamsheeVazza : UPPER should definitely work because we used it. If you want multiple conditions you need to use like below
(upper(trim(users.customproperty1))=upper(trim(accounts.name)) or upper(trim(users.customproperty2))=upper(trim(accounts.name)) or upper(trim(USERS.CUSTOMPROPERTY59))=upper(trim(ACCOUNTS.NAME)) or upper(trim(USERS.CUSTOMPROPERTY60))=upper(trim(ACCOUNTS.NAME)) or upper(trim(USERS.CUSTOMPROPERTY61))=upper(trim(ACCOUNTS.NAME))or upper(trim(USERS.CUSTOMPROPERTY62))=upper(trim(ACCOUNTS.NAME))or upper(trim(USERS.CUSTOMPROPERTY63))=upper(trim(ACCOUNTS.NAME))or upper(trim(USERS.CUSTOMPROPERTY64))=upper(trim(ACCOUNTS.NAME))or upper(trim(USERS.CUSTOMPROPERTY65))=upper(trim(ACCOUNTS.NAME)))
12/07/2023 10:37 AM
Please share logs where it print correlation - in ending of job logs
12/07/2023 10:40 AM
Please select