Hi @LakshmiPravallika, Did you try RowNum() function (creating a common identifier for both using enrichment and then doing the exclusion)? Let me know if that worked for you. Thanks,  

Hi @sah_, For 3rd point it will be like creating a link between those row number. Attaching snip as well:  Thanks,

Hi @sah_, When you load the CSV using the Data Loading (file) activity, just skip selecting a schema — Campaign will automatically create a temporary table for you behind the scenes. This is great if you don’t need to store the coupons long-term or reference them later.Here’s how you can handle the ...

Hi @SkylerQu2, Since you want to send variables from the delivery to the ‘ccStageAlerts’ workflow, here’s what I’d suggest: - Use a JavaScript activity inside the workflow itself to handle and process those variables when the workflow runs.- From the delivery side, it’s not really possible to call x...

Hi @RaphaelBe2, Even if you don't see the notification block in your delivery template, Adobe Campaign might still be adding it automatically. This usually comes from how your mobile app is configured under Administration > Platform > External Accounts. If you're using FCM (Firebase Cloud Messaging)...

Hey @LAR1985, You're doing the right thing by restricting sends to between 21:00 and 08:00 using the contact date formula. The issue you're hitting makes sense though — Adobe Campaign evaluates that formula only for the "First wave", and then the system handles the rest of the waves based on fixed i...

Hi everyone, One common issue I see often in Adobe Campaign is how risky it is to make schema changes—especially on core tables like nms:recipient.Changing things like primary keys or data types can break references, cause data loss, or even crash the system.It’d be super helpful if ACC had a Smart ...

Hi @AntonaccioM , Can you change the primary key in `nms:recipient`?Unfortunately, no — it’s not safe or supported.The `@id` field is used everywhere in Adobe Campaign (logs, tracking, deliveries, etc.). Changing its type (e.g. from `long` to `string`) would break those internal links and could corr...

Hi @LakshmiPravallika, Since your transactional messages are targeted using nms:recipient, and the lists you’d like to exclude are based on different schemas (nms:address and a Redshift schema), you won’t be able to reference them directly in the delivery for exclusions.Instead, use this approach:- ...

Hi @Wilnaweb1,You're running into this error because the @ID field in your schema (sam:ape_controlStg) is set to auto-generate as a UUID:<attribute name="id" type="uuid" autopk="true" autouuid="true" ... />This means Adobe Campaign Classic automatically handles the primary key (@id) when new records...