Arrays and upserts (partial record updates) haven't been a good mix. I've never seen anyone be happy with the results even after extensive attempts. My recommend is to break out those arrays to a separate schema/dataset where you don't need to use upsert.  Replace the full array each time any potion...

I've also found that sometimes arrays are the only valid data structure that I can use for my data, e.g. lists of things per profile. But instead of using CSV format, it's easy to get a sample JSON record for your target dataset by going to the Schemas > Browse page, selecting the target schemas, an...

You can... but I'm unclear on why you would want to. Normally we reserve the list of namespaces for pseudonymous profile deletion to device and cookie namespaces. Plus other relatively short lived identity namespace. So ECID, AAID, AACUSTOMID, IDFA, GAID, etc. If you have other longer lived identiti...

Here's an additional option:"Multi-Forked Event Expiration Strategy using DataStream in AEP RTCDP"https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform-blogs/multi-forked-event-expiration-strategy-using-datastream-in-aep/ba-p/593224 Can be used for different EE-TTL as written, b...

Best practice is to set a minimum length greater than zero on string fields in your schemas. Always. There's never a time where a zero length field value is a better choice than a null.  The AEP UI now adds "minimum = 1" by default when you add a new string field to any schema for just this reason, ...

Another way to look at it is that you cannot use SQL statements such as INSERT or CREATE TABLE without a license to Data Distiller. Nor can you schedule any queries without that license. Without a license to Data Distiller you are limited to interactive SELECT statements executed in the AEP UI or vi...

Null values are fine and expected for fields that aren't marked as required.But while zero length strings are also allowed, these should be prevented to avoid complicating audience rule definitions. Best practice is to set a minimum length value on the schema definitions of string fields.But be care...

It's expected behavior and no, you cannot bypass this.   When deciding on whether to mark something as an identity you need to first evaluate whether it's truly unique for the level of profile granularity that you want. In your case you seem to want GlobalID as the determination of profile granulari...

SQL tools typically have a way to export query results to a local file system, e.g. the psql tool has a \g option for this that works with Query Service.

Just saw this, so will answer now as a reference for future searches. Yes, you can create new types of entities in AEP now. The concept is called "multi-entity segmentation", and as you describe this allows you to create lookup data that can be tied to both XDM Profile schemas and also XDM Experienc...