Below example for csv, but fundamentally the same as a table.csv file creating the identityMap from one field, one namespace:to_object('CUSTID',to_object('id',trim(CUST_ID),'primary',true)) Another doing a multiple fields with the same namespace:to_object('CUSTID',arrays_to_objects('id',explode(conc...

@akwankl In Next is the function. Use Offer End Date In Next x to y days Use Offer Start Date In Next x to y days.

@sheejo Ignore the title, I've asked them to change it. It describes how to relate the loyalty (profile) schema to the hotel (custom class) schema.  That relationship is 1:M.  One hotel can have many people.

Did you try using the this? It shows how to create a relationship between a person and their favorite hotel. https://experienceleague.adobe.com/docs/experience-platform/xdm/tutorials/relationship-ui.html?lang=en  

It has nothing to do with AEP.  The CSV files structure does not support Arrays.  If you look in your key column, you see you have a comma in the field value.  That for a CSV file is interpreted as a field delimiter. While I recommend using a JSON file instead, if you have no other option, you need ...

Unfortunately, I haven't needed to dive into it at that level yet, so don't really know which to recommend. I put them both in one schema to see the overlap (Web SDK includes all of Mobile except for one area, which is the application object).  So my initial response is you could use them both w/o a...

I'm not sure why you would want to do that.  You may be getting into some compliance difficulty if you hold onto data in some sandboxes while the expectation of the Data Subject (i.e. your customer) is that all data is being deleted.

Here is the Mobile Field Group: AEP Mobile Lifecycle Details Tutorial: https://experienceleague.adobe.com/docs/platform-learn/implement-mobile-sdk/app-implementation/lifecycle-data.html?lang=en   You might also try looking at the Web Details Field Group for this.  Here is the link: https://experienc...

The mergePolicyId is optional and not needed if you only have the one default merge policy (which I highly recommend).