Nível 1
Nível 2
Faça login na Comunidade
Faça logon para exibir todas as medalhas
Hi Adobe Community,
I need to bring in a new table in AEP that doesn't contain any of our primary identifiers (table A). So, the plan is to bring it in as a lookup table. However, the only field that I can link this new lookup table to in my system is a field that is already in a lookup table (table B). In the UI, I don't see a way to create a relationship on this field in table B which makes me think that you cannot create a lookup on a lookup. I feel like this should be possible since a lookup is essentially just a join on that field. If I make this field a primary identity in table B, would I be able to create a relationship with table A?
Thanks,
Nick
Os tópicos ajudam a categorizar o conteúdo da comunidade e aumentam sua capacidade de descobrir conteúdo relevante.
Visualizações
respostas
Total de curtidas
Hi @NickMannion ,
Yes - but only if the field in table B is set up as an identity (profile-enabled). If it’s just a regular attribute, you can’t create a UI relationship from A to B.
Reference:
https://experienceleague.adobe.com/en/docs/experience-platform/xdm/tutorials/relationship-ui
Thanks,
Ankit
Custom query in Query Service using SQL?
Visualizações
respostas
Total de curtidas
HI ,
In our current setup, we use relationships for AJO lookup data and leverage them accordingly. For non–profile-enabled datasets, we use the datasetLookup function for email personalization and offers. I also noticed one more approach https://experienceleague.adobe.com/en/docs/journey-optimizer/using/data-management/lookup-aep-data
Thank you,
Uma
Visualizações
Curtida
respostas
Visualizações
Curtida
respostas
Visualizações
Curtida
respostas
Visualizações
Curtida
respostas