Expand my Community achievements bar.

creating array of objects

Avatar

Level 8

Is it possible to create such a data structure in order to iterate over this in AJO? Everytime I create something I am not allowed to save it. 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

6 Replies

Avatar

Administrator

@Asheesh_Pandey @AnkurSingla @Jennifer_Andrews @yumera @Jennifer_Dungan @VaniBhemarasetty @Abhishek_Narula25 @user48 @shuaib27811 @PratheepArunRaj Kindly take a moment to review this question and share your valuable insights. Your expertise would be greatly appreciated!



Kautuk Sahni

Avatar

Level 2

Hello, @Michael_Soprano,

 

I am not exactly sure if this is helpful, but, as I understood you properly, in AEP, in Schemas, youc an create an array of objects in the following way: 

GigiCotruta_0-1734437897655.png

We are using it and it works without any problems. 

 

Hopefully it helped, 

BR.

Avatar

Community Advisor

Hi @Michael_Soprano 

afaik - at least I have come across this in the Adobe videos a while back - there is/was only one array of objects supported which is the productListItems.

 

Maybe this has changed, but your experience seems to reflect this. Would be great if Adobe could confirm this.

 

https://experienceleague.adobe.com/en/docs/experience-platform/xdm/data-types/product-list-item

 

Cheers from Switzerland!


Avatar

Level 8

I would like to create custom array of objects. I created for now custom Data Type which I can put into array and testing that in AJO. Would come back with feedback... 

Avatar

Employee

@ Michael_Soprano , I'm not quite following what your ask is and its use case.  You can fully create an array of objects within XDM as @kautuk_sahni outlined.  Could you describe where you encountering the issue you are raising within AJO and the context of the use case?

Once I have that detail I can likely provide some better direction and/or input. Thanks!

Avatar

Level 9

@Michael_Soprano Adobe suggests using simple XDM and limiting nesting in terms of object, specifically if felid is going to be part of Primary/Secondary identity - should not done, rather simplify ERD/XDM to get required felid. If you still need to do think of scalability in terms of future requirement