Hi and thanks again. Ended up with a dirty workaround, appending the data to the actual textmessage (with a typology rule: delivery.content.sms.source += ':!:!<%= recipient.xxx %>') and then removed it in the smsConnector-script. Didn't find any way to add a separate variable that were accessible fr...

Hi Jon and thanks for your reply, I didn't know that it is possible to modify built in js-code. It says "This is an application built-in object. It cannot be modified". How do I edit this file? Just overwrite it directly on the linux-server? If yes, will this change be overwritten on every build upg...

Hi all,We have 5 different instances of Adobe Campaign Classic. 4 of them contain one brand in each, and the 5th contains 10 brands.We're using the builtin Adobe Analytics connector to send delivery data to analytics, but we can't seem to split the data based on sub-brand. We would like to see the 1...

Hi Jon and thanks for your advice,This is the first time I am working with js-typologies. Do you know what kind of objects that are available in the context (apart from delivery)?Is the recipient-data-table available in this context (so I can just refer to recipient.[columnName])? The optimal soluti...

Hi,I would like to add data from the recipient-schema to each SMS-delivery, without using a personalization-block in the message GUI. The added data should not be a part of the text message, it will be used for logging purposes. The only workaround I found is adding it as a personalization block and...

Hi again, just wanted to give you an update on how I solved it.var loadedOffer= NLWS.nmsOffer.load(offer.@id); var offerToEdit = new DOMDocument.fromXMLString(loadedOffer.toDocument().toXMLString()); offerToEdit.renameNode(offerToEdit.getElementsByTagName("view")[0].getElementsByTagName("testTagBef...

Hi Milan and thanks for your suggestion! However, I will not be able to use the save function after converting to a DOMDocument, right? Do you got any nice solution for this as well? Edit: I found ot I could do a sqlExec update on nmsOffer MDATA.

Hi everyone,I am trying to rename a js property (within the view object) and would like to replace the view-object with a new edited object, but I am struggling.var offerToEdit = NLWS.nmsOffer.load(offer.@id); //loads the specified offer fine offerToEdit.view = updatedViewObjectWithAnEditedPropertyN...

Hmm, yes that is possible, but then the eligibility-criteria would consist of nested "OR is included in listDefXX".

Thanks for the feedback! Please share your thoughts on how we can avoid this We are using specific lists for every offer and the list synchronization is taking a lot of time.The aggregated list definition column was a suggestion from a Adobe SME to avoid the list synchronization problems.