Adding a JSON document to the custom data seems like it could be a valid solution, but I'm not entirely confident that's the recommended approach here. I'll need to double-check the best practices for logging customer orders in SAP Customer Data Cloud.
Updating the profile schema according to the order data structure sounds like a good idea. That way, the order information can be directly tied to the customer's profile. I'll make sure to review the schema requirements closely.
Hmm, I'm a bit unsure about this one. Modifying the accounts data schema to add an array of orders attribute could work, but I'm not sure if that's the recommended approach. I'll have to think this through carefully.
I think the best approach here is to add a custom type to the Data Store and provide a UID when storing customer order documents. That seems like the most straightforward way to keep a log of the orders.
Hmm, I'm a bit unsure about this one. I know hash functions are used for storing data, but I'm not sure if that's the full definition. I might need to think this through a bit more.
Option B looks like the way to go. Adding a custom type to the Data Store and providing a UID for the customer order documents seems like the most straightforward approach.
Lina
3 months agoLeonor
3 months agoBeckie
3 months agoLawrence
4 months agoGoldie
4 months agoScarlet
4 months agoDoretha
4 months agoRima
4 months agoDouglass
5 months agoHannah
5 months agoDevora
5 months agoLauran
5 months agoHaydee
5 months agoMacy
5 months agoAlfred
1 year agoSabra
1 year agoCarman
1 year agoMinna
1 year agoZana
1 year agoAnthony
1 year agoKaron
1 year agoLarae
1 year agoKristofer
1 year agoLayla
1 year agoFairy
1 year agoNoemi
1 year agoVicki
1 year agoNikita
1 year agoBrett
1 year agoIsaac
1 year agoCharlesetta
1 year agoJesse
1 year agoDalene
1 year agoAnna
1 year agoMagnolia
1 year agoKatheryn
1 year agoShenika
1 year agoMarge
1 year ago