How to create or update CDC account via dataflow to trigger webhook without setting loginIdentifier

[Rvanjari]

Hi all,

I'm working on a CDC DataFlow where the goal is to either create or update user accounts using the accounts.importFullAccount API. As part of the same DataFlow, I also need to trigger an update action to ensure that webhooks are fired.

However, I'm running into an issue where using the gigya.generic or gigya.accounts writer steps causes the loginIdentifier to be automatically set. This is problematic, as I don’t want the loginIdentifier to be defined at this stage—my objective is to simply create a registered account without setting the login identifier.

Is there a way to configure the DataFlow so that:

• The account is created or updated using accounts.importFullAccount
• The webhook is triggered through an update
• But without setting or modifying the loginIdentifier field?

Any guidance or best practices for handling this would be greatly appreciated.

Thanks in advance!

[Oleh_Ilchyshyn]

Hi @Rvanjari,
I understood what you were trying to reach and fully reproduced it on my side. 
gigya.accounts or gigya.generic writer steps don't cause the loginIdentifier to be automatically set by default. Maybe somewhere in your dataflow scripts/steps you have a loginIDs implementation? Please review it.

Meanwhile, I will provide you with the dataflow I've created for your case.
It consists of 4 steps:

Let's go through each of the steps in detail.

STEP 1 - Initiate record (record.evaluate)

STEP 2 - gigya.importaccount (datasource.write.gigya.importaccount)

STEP 3 - After import logic (successful). Return UID (record.evaluate)

STEP 4 - gigya.account (with nothing - to trigger webhook) (datasource.write.gigya.account)

When you execute this dataflow multiple times, one by one, you will notice that Users (with different UID) will be created in CDC (without loginIdentifiers - loginIDs)

It confirms that they don't have loginIdentifier (loginIDs), as in another case, you couldn't see them 3 there.
The same, from an API perspective.

Let me know if this could help you to cover your case.
If no or any other questions/clarifications - let's discuss it in comments under that post.

Regards,
Oleh.

[KunalBansal]

Hey @Rvanjari,

Trigger Webhook with minimal updates - use a custom gigya.generic step with a lightweight accounts.setAccountInfo call, but exclude loginID, email, username, or loginIdentifier in the payload

Feel free to reply for further queries. If it helped, mark thread as accepted solution.
Thanks & Regards,
Kunal Bansal, SAP CX SME
https://www.linkedin.com/in/thekunalbansal