Hi @bjoern__koth , Thanks for your response, your solution using Optional Chaining is really powerful. The problem we have is that when accessing arc.event.xdm.hello.world through code we are not even able to publish the changes: There was an error minifying your custom code.Referenced DataElements ...

Hi Manoj, Thanks for your prompt response. Your solution makes sense but it requires one rule per brand (I have more than 20 brands in some cases). Also, I would need a Data Element per each XDM path, which is something I would definitely like to avoid. Have you tried to access "arc.event.xdm" direc...

Hi there, I am trying to use Event Forwarding to send data to other systems dynamically. The scenario is multi-brand, so I have different XDM schema fields referring to the same concept (e.g.: identities.brand1.ecid, identities.brand2.ecid). I want Event Forwarding to adapt the request depending on ...

Hi there, I have an AEP profile dataset with some million CRM records being connected to CJA. Most of profiles do not have events tied to the CRM ID, so we cannot view them in Analysis Workspace (as Adobe FAQ explains). However, the client needs to analyze all the customer records in CJA no matter t...

Hi @gmadala, I've found the same issue when ingesting historical data coming from Adobe Analytics source connector. Currently, you can map AA data to XDM through this source connector, but this will not work if you want to map evars/props to Adobe field groups or your schema does not have the Analyt...