Hi,Unfortunately no, i haven't been able to find a solution to this as of yet.I'd be very interested myself to know why this is happening, as this process is something that i've used in the past and was working fine, so it might be a case of something changing in latest versions of Adobe.If anyone has any info around this, it would be really appreciated.Thanks,Solon

Hi Pablo,Appreciate this is the case for standard schemas, but in my case i'm referring to a content management schema.Reading through the online documentation Use case: creating content management , there is no mention or reference of manually defining any primary keys in order for this to work. As mentioned in my previous comments, i've previously managed to get this to work, by following the documentation and without defining any primary keys, so i'm curious if latest versions of Adobe Classi...

Hi,I'm 99% sure that option was never available in an enrichment activity The way i usually do it, is i use a query to select the data and fields i need to aggregate, disable the primary key and then do the actual aggregation and grouping in an enrichment. After that, if i need to do any joins with any base tables (e.x recipient table), i query that table separately and bring both transitions into a new enrichment, and then do a join using Add Data -> Create a link in the Enrichment.Thanks,Solon

Hi,I didn't specify any primary keys, manually atleast. My understanding is that Adobe autogenerates a Primary Key anyways.I found that i had to manually add the below, and it seemed to have rectified the issue:I'm now experiencing another issue though, where when i reference any of the content fields in the Javascript Template by using <%= content.@FIELDNAME %>, i get the following error:As an example, i'm referencing <%= content.@firstBanner_Alt %> in the Javascript Template, but i get an erro...

Hi Vipul,Worked perfectly, thank you for your assistance.Solon