MAP dataType in AEP Schema

Hi @pradeep-jaiswal,

The problems that I see with the Map object that @tof_jossic sent the documentation are the restrictions:

• Map types MUST be of type object. --> No problem
• Map types MUST NOT have properties defined (in other words, they define “empty” objects). --> No problem
• Map types MUST include an additionalProperties.type field that describes the values that may be placed within the map, either string or integer. --> From your example, that's a problem as you defined a timestamp date value.
• Multi-entity segmentation can only be defined based on the map keys and not the values. --> That's a big problem IMO. I suppose you want to do your segmentation based on values, not keys. That's the main reason on why I would suggest you a normal object, not a map one. It does not have the limitations that this does.
• Maps are not supported for account audiences. --> I don't know if it is your case.

Hi @pradeep-jaiswal,

Were you able to resolve this query with the help of the provided solutions, or do you still need further assistance? Please let us know. If any of the answers were helpful in moving you closer to a resolution, even partially, we encourage you to mark the one that helped the most as the 'Correct Reply.'

Thank you!