Hi @AnkitaVi1 ,The issue you're encountering—where the deliveryProvider.id (Routing/External Account) isn’t updating—likely stems from how Adobe Campaign handles the deliveryProvider field. In the nms:delivery schema, deliveryProvider is a link to the xtk:provider schema (or nms:externalAccount in s...

Hi @Sujith_02kumar,It’s not considered best practice to keep the workflow on hold for 1-5 days to identify the winning delivery. However, you can still determine the winning delivery by using the following JavaScript code:// Fetch KPIs for each delivery manually entered or from workflow var delivery...

Hi @at7140,1. Optimize the QueryDef ExecutionThe current pagination approach is solid, but the query itself might be slowing things down. Here’s how to refine it:Minimize Selected Fields: Only select the fields you absolutely need. If you’re processing @id and @email, don’t include unnecessary colum...

Hi @at7140,To handle large datasets (e.g., 200,000 records) in Adobe Campaign and ensure your JS works correctly, you can use the following strategies:1. Paginate Queries with QueryDefInstead of fetching all 200,000 records at once, use pagination to process the data in smaller chunks (e.g., 10,000 ...

Hi @AnkitaVi ,Why It Works for Your Client Without a Package:Your client’s instance likely has a configuration that allows unrecognized SQL functions to be passed directly to the underlying database engine (e.g., PostgreSQL, SQL Server, etc.). This is controlled by the "XtkPassUnknownSQLFunctionsToR...

@JorgeTo1,Second option would be Use a Typology Rule (Dynamic Control)If you want more flexibility without modifying templates or schemas permanently, you can create a typology rule to dynamically set useBlackList to "no" during delivery preparation.Create a Typology Rule:Go to Administration > Camp...

@JorgeTo1,Modify the Delivery Template:The simplest and most practical way to change the default behavior for new deliveries is to update the delivery template(s) used to create them. Delivery templates inherit properties to new deliveries, so setting useBlackList to "no" in the template will ensure...

Hi @stephaneAD,You can use sysFilter to Restrict Schema Access.The sysFilter element in a schema allows you to define conditions that control who can read or write to the schema. By setting a readAccess filter, you can prevent non-authorized users from even seeing the schema in the interface (e.g., ...

Hi @KrishnakumarD1,Adding a custom input field to an SMS delivery to store an image URL involves extending the schema, modifying the input form, and ensuring the field is available in the delivery configuration.1. Extend the Delivery SchemaThe SMS delivery configuration is tied to the nms:delivery s...

Hi @Cl4ud,Unfortunately, there isn’t a direct configuration in Adobe Campaign Classic v7 (or v8) to prevent the DCE from adding these tags when text is entered in the visual mode. This behavior is baked into how the editor processes content—it assumes you’re creating a complete HTML document. Howeve...