Hi Salvatore,Not sure to fully understand, sorry. But I will try to give some ideas, in addition of dattarays70361342​ accurate answer. Il you need triggered mails raised by external events, but not by using Message Center, please have a look on pipeline mechanism, in case you use Adobe Analytics (O...

Hi Giuseppe,Unfortunely, the JSAPI.chm documentation is quite light for this method but only 2 arguments.Well, I give it below, to avoid further misleading. florentlb​ feel free to suppress it if it is not allowed to share, as far as I understand.GetMirrorURLObtains the URL of an HTML mirror page. S...

Hi Saikattk,The documentation is the JSAPI.chm subject to license. Do you own it?Regards.J-Serge

PS: if you intend to use Message Center messages, the delivery mapping is nms:broadlogRcpEventHisto

Hi Salvatore,Your code works perfectly on my instance.Please check if your delivery mapping is using nms:broadlogrcp, perhaps are you using a specific one?Please use the Generic query editor tool to have a look on the broadlogrcp content, and especially the eventDate column, to be sure that it is th...

Hi Kaushal,Please may you do a test with the @addressSpecific element of nms:subscription, even if you let the optin at contact level (nms:recipient)?So you test by creating a service for each av:sourcesystem or ad:source (you mention both schemas, so I wonder which is correct).Regards.J-Serge

Hello Kaushal,I suggest you an alternative, that we choose to implement and it works fine, because mostly based on standard/factory Adobe Campaign default tables: using NmsSubscription, services can either your sources or other notions, and so you achieve your delivery targetting by using the standa...

I confirm the issue: it takes too much time than necessary with Export template tool; even if subject is a shared information of all messages of a delivery, the operation is probably bad managed by the Export template tool, probably because of the mData field management itself. For my "small" server...

I guess that the performance response time issue is probably due to the target dimension that you use (broadLogRcp schema, according to your first screenshot) and the internal algorithm used by Export template activity.With the join done to delivery schema, in order to get the subject, even if it is...

And also I must mention that I was wrong, you can select for extracting the XML field (target/mailParameters/subject) from an Extract activity. So it remains not possible from queryDef and Query/Enrichment activity only.RegardsJS