Hi @Mrityunjay The error indicates that when trying to access the recipient record, one of the relations link to the recipient (via the JOIN clauses) doe snot exist. It could be that link is defined as 1:1 instead of 0:1. Saying that you've got a strange JOIN clause on xtkFolder, you got it twice as...

Hi @jayakrishnaaparthasarathy  To sum up you added new fields on an existing schema and you've done 2 ways for the datasetAdding the fields in an existing datasetCreating a new dataset which just the added fieldsAm I correct?Remember that data in AEP Data Lake are on insertion basis, so depending on...

Hi @Manpreet1 You can't do that, especially on Recipient as you will break ALL the links that exist around the recipient entity. You can have ONLY 1 Primary Key. Define your 2nd key as a unique index instead of a primary key. it will achieve the same result and you won't break the standard data sche...

Hi @csoile Sure no worries on the 2nd element, it's workflow optimisation that is useful to know if case performance start to creak in. The steps are:Go to Property tab of Query and select the element in ResourcesSearch Tracking Log and Select nms:trakcingLogRcp In target, Select Profile Doing suhc ...

HI @csoile Yes for the field to use which holds the URL however the query won't be efficient and performance if you have 2 exist clause. Make sure you the Source URL criteria in the same Exist clause that the delivery campaign criteria... Also, since I don't know your volume of Profile, using Exist ...

Hi @csoile To get the Operations associated to a click, from the tracking Log, you would drill down to the Delivery and form the Delivery you would drill down to Campaign.You have to go to Advanced mode in the Rules Editor and select the arrow on the right of the Delivery field, scroll down to find ...

Hi @ASNeelima Resource is the entity where the selection criteria will apply. In SQL mode, this corresponds to the entity set in the FROM clauseTargeting is the entity that will be returned, in SAL mode, this corresponds to the entity in the SELECT clause.By default Targeting is the Resource entity,...

Hi @Zamwize  Sadly I don’t think you can force a specific order to execute things. If for instance you have a Fork activity with x branches with one query in each branches, the query activities are executed sequentially and once the query in a branch is executed, the next activity will be executed w...

Hi @derekw42533281 you could use the Test activity that contain the total number in the audience, so if you expect always more than xxxx records you could send an alert and then continue the process. it might give you what you ´re looking for. thanks. Denis. 

Hi @Nikhil719 Could you elaborate the use case because I am not sure to understand the topic? have you got in mind People Based Destination type of scenario for instance?ThanksDenis