table and data within will remain in database when you delete the schema from AC.
If you want to delete it from DB as well initiate Tools/Advanced/Update database structure which will recognize that you deleted schema and prepare drop statements for your database and can confirm del...
I am not sure that anybody offered better way (from technical perspective) then using a mirror page feature.
On delivery level you can force Mirror page creation and get links via function:mirrorPage = nms.delivery.GetMirrorURL(record.@deliveryId,record.@broadlogId.toXMLString());
you should not use PK of the table (Leads.id) when you sending an email.
Check if the table has Encrypted identifier column (@cryptedId) like Recipient table has and try with that.
Hi @shaohong I am not sure there is an easy way for it. Personalization is done on the fly by MTA.You can enable mirror page option on delivery level and have the preview of the content for the time you define as mirror page lifetime.
Honestly, I am not sure but think it does not deal with FDA databases when connectors are disabled. You may check if inside of connectors you pushed all necessary functions towards FDA databases and check if there are improvements.
It depends how often your clean up workflow is sche...
just be carefull here.
Since the intention is to drop all the objects for a schema, why not just drop and recreate that schema with all the required privileges (rather than dropping each and every objects.
drop user <user_name> CASCADE;then re-create that schema again.
if you want t...
Hi @Mrityunjay, if understood question properly you can use Incremental query node to select new customers. First time execution will select all existing customers (or add condition on create date) and every new execution will return you only new customers which you can follow with Subscription Serv...