Hi @itsMeTechy ,In the UI, merge policies have a user-friendly ID (human-readable name).But in the profile snapshot dataset name, you’ll often see a suffix like numbers and dash included into it (real internal identifier).Real internal identifier gets used when a snapshot is generated.You can list a...

Hi @itsMeTechy ,Yes, when multiple merge policies are defined in AEP, each profile snapshot table is created per merge policy, because each merge policy produces a different view of the unified profile. To differentiate which profile snapshot table corresponds to which merge policy, you can follow t...

Hi @Ikmo7 ,You can follow 2nd step which I have mentioned in previous reply. ThanksAnkit

Hi @BenjaminPu ,Directly through UI option not available as of now but Segment Builder APIs are there.Reference: https://experienceleague.adobe.com/en/docs/experience-platform/segmentation/api/segment-definitions ThanksAnkit

Hi @AEPuser16 ,723456789123 - far exceeds this limit, leading to data corruption or overflow, hence the negative/incorrect values you are seeing.In your AEP schema, you used the 'integer' data type, which maps to a 32-bit signed integer in many systems, including Adobe's internal mapping logic.Refer...

Hi @AEPuser16 , 1) AEP does not provide a direct "duplicate schema" or "clone schema" feature in its UI or APIs.Recommended approach to clone or duplicate a schema safely:Export the existing schema definitionModify the exported schema JSONCreate a new schemaValidate the new schema2) Changing the dat...