Dataset lookup in AJO not working | Community
Skip to main content
arpan-garg
Community Advisor
arpan-gargCommunity Advisor
Community Advisor
December 11, 2024
Solved

Dataset lookup in AJO not working

  • December 11, 2024
  • 2 replies
  • 3217 views

Hi Team,

Recently a new feature was introduced in AJO which allow you to lookup aep data while targeting customers via email. https://experienceleague.adobe.com/en/docs/journey-optimizer/using/content-management/personalization/lookup-aep-data

I created a profile schema and a lookup schema address both enabled for profile plus also created datasets for both(also enabled for profile). Profile is linked to address lookup via a address id. In audience creation, i see that profile is linked to address properly (i can see all fields of address lookup when i select profile attribute which means the relationship is set properly).

 

However in AJO when i send an email to the customer and fetch his address details via the address id , i always get empty address.

 

Did anyone tried this already?

 

Just for information: I have already enabled dataset for lookup as mentioned on the document 

 

Thanks,

Arpan

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Arnas_Valeika

@arnas_valeika  - 6759606d0561a02aef3d10aa 


Hi @arpan-garg 

There was a JIRA created for this issue, let me also answer here:

Initially - dataset ingestion was re-enabled multiple times, and when ingestion is enabled, then we ingest whole dataset. And at that time there were multiple records for the same testing Id.
And we get a random record having the test id in this case.

Recently I saw few updates to the dataset, for the same testing id. And service returns the latest update, as expected.

If dataset ingestion doesn't get disabled, it should continue working as expected as long as update batches have unique ids.

2 replies

I
Adobe Employee
IvanMi1Adobe Employee
Adobe Employee
December 11, 2024

HI @arpan-garg -

Couple of questions. 

 

1) Does your schema have "addressID" set as the primary identity? 

2) Do you have unique "addressID" for each row in the dataset? 

3) When you used the API call to enable your dataset for lookup did you get a Success 200 message returned? 

4) When using the function in personalization editor did you get any validation errors? 

5) Did you make sure to use the full path from the schema when referencing the fields of data you wish to bring in? 

6) You can set the dataset look expression to be required="true" which should result in an exclusion if a match is not found.

7) Did you try putting in a static key into the expression to see if you can just get a match to work? 

 

Make sure that if you are using a dynamic attribute for the ID that you remove the quotes. i.e. id=profile.customer.addressID. if you have id="profile.customer.addressID" it will look for this static value and find no results. 

    arpan-garg
    Community Advisor
    arpan-gargCommunity AdvisorAuthor
    Community Advisor
    December 12, 2024

    @ivanmi1 ! Your last suggestion, to avoid surrounding the id with quotes, helped me resolve the issue—I was making the same mistake. However, I would greatly appreciate it if Adobe could address this inconsistency in their documentation. In this guide, it is still mentioned to use quotes.

     

    Regarding your second point about ensuring only unique entry exists for each address ID, I encountered a scenario where a customer's address changed from Texas to Arizona. However, the lookup always returns the old address (Texas). How can this situation be managed? Lookup functionality will only be truly useful if it fetches the latest data from the dataset, rather than the first record.

     

    What do you suggest?

      arpan-garg
      Community Advisor
      arpan-gargCommunity AdvisorAuthor
      Community Advisor
      February 19, 2025

      Hi @arpan-garg 

      There was a JIRA created for this issue, let me also answer here:

      Initially - dataset ingestion was re-enabled multiple times, and when ingestion is enabled, then we ingest whole dataset. And at that time there were multiple records for the same testing Id.
      And we get a random record having the test id in this case.

      Recently I saw few updates to the dataset, for the same testing id. And service returns the latest update, as expected.

      If dataset ingestion doesn't get disabled, it should continue working as expected as long as update batches have unique ids.


      Hi @arnas_valeika  - It works now. Good to know the logic on how it works, no where in the documentation was it mentioned that we should not renable it for lookup multiple times and since this functionality is new , i agree we did it multiple times to test

      Sukrity_Wadhwa
      Community Manager
      Sukrity_WadhwaCommunity Manager
      Community Manager
      January 17, 2025

      Hi @arpan-garg, 

      Can you please share the solution that Ivan helped you achieve with the community?

      Thanks!

      Sukrity Wadhwa
      arpan-garg
      Community Advisor
      arpan-gargCommunity AdvisorAuthor
      Community Advisor
      January 27, 2025

      Hi @sukrity_wadhwa  - Haven't got any response on this from @ivanmi1 , still waiting.

      I
      Adobe Employee
      IvanMi1Adobe Employee
      Adobe Employee
      February 26, 2025

      @arpan-garg @Will need to get a support ticket raised to investigate the details. How are you loading the new batches of data? The revised data should be available for lookup once the batch is completed processing 

      Terms & ConditionsAccessibility statement

      Loading footer...