Hi Darpan,Yes its possible to extend like this. You are trying to check data from extended schema(xyz:recipient) that's why the error.Kindly check nms: recipient data tab and from there you will have your extended columns from(xyz:recipient) and also data for the same.Hope this helps. Thanks,Kapil

Hi Sree,I am not sure i understand your problem statement correctly. If I want to avoid multiple if else inside Email delivery what i will do is to create one personalization block  and include that block in delivery source code.Something like below Creating PBUsing above created PB in Email source ...

This is very basic, sometime it's very annoying when you have 30-40 variables to add as an output columns in enrichment activity and you have to click each columns separately.  Multiple selection in one go should be allowed ? Any thoughts?  I

Hi Venu,Please check this thread Count of Message prepared greater than ISSUE

Hi Venu,This may happen when you have several personalization combination for a contact. Please check your personalization definition. Also, Try  by including duplicates in the "to" section of the delivery. Let me know if this works. Thanks,Kapil

Hi ,As mentioned above, the best solution will be to create a technical workflow with[Option1] : Scheduler and logic to export data in file and then send the file over SFTP or ..location. And Yes, you can design your logic in export workflow to include historical campaigns as well. It's all depends ...

Hi ,For Adobe Classic as well you can use incremental query on delivery logs. Alternatively,For creating daily report create a technical workflow with- Scheduler- Query activity with JS in advance tab which take time from global option(Store last run timnig og this worklfow) somthing like belowvars....

Hi Arjun,Please follow below link very useful Workflow best practices

Hi Ametha,Try below code and change and add schema based on your requirement. var cnx = new HttpSoapConnection(serverName, "UTF-8",0) var session = new SoapService(cnx, "namespace:schemaName")  session.addMethod("MethodName", "namespace:schemaName#MethodName",                                    <par...

Hi Saurabh,If you want to automate the package migration process based on API executable commands. you need to create one new schema and expose two methods for export and import  and then create JS to write logic for both functions like for Import will be     a. Saving incoming request in schema for...