on 2023 Oct 30 10:39 AM
Hi All ,
I am working on a below scenarios where i am facing challenges with duplication of site accounts
Scenario 1
Where there are multiple accounts created in SAP CDC , the account has same email Ids without password , how can i link all the site accounts?
To mention all those site accounts are created via file import ( DataFlow) , so not updating the loginIDs against it , future senarios can be controlled , but need a solution to remove the existing duplicate account.
Scenario 2
Having multiple accounts in SAP CDC , one with password and another without password , both site account , i tried to use the accounts.linkAccounts REST API , it works fine when i know the password , but what in case i dont the password , does the hashed password works?
to mention the accounts already exist without password are created via file import and the one created later is via portal account with password.
Need a way to link the site accounts to remove duplication in SAP CDC
Many Thanks,
Ruchita
Request clarification before answering.
Hello ruchita.vanjari,
"Manually i can delete , but do we have a way we can do it via REST API ? link those and have one single record." - You don't need to do it manually. You could create another dataflow to search contact accounts based on some condition(to distinguish wrongly migrated from valid existing ones) and just delete them using accounts.deleteAccount REST API.
Regarding linking - not sure that it will work for you. You mentioned, that accounts are without credentials. As accounts.linkAccounts REST API documentation says: "method first validates the login credentials, then merges the data". So, not sure that it is possible to merge without validating first by CDC.
"i have a scenario where a customer account in already in CDC without password and later he use UI to create his account with password. to have that scenario included i cannot add loginIDs." - I've got your point. You follow the requirements to keep the user in CDC with further possibility to register. If you kept loginID - you wouldn't do it.
But to avoid the issue with duplicates, I would suggest keeping such types of accounts as Lite Accounts. In this case you can create accounts with data. Later, when you are trying to register someone via portal, for example, with the same email, it automatically merges lite into full.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.