Hello @wALF Can you give a try to this script (for example in a JS workflow activity) please :var schemaQuery = xtk.queryDef.create(<queryDef operation="select" schema="xtk:schema"><select><node expr="@namespace"/><node expr="@name"/></select></queryDef>); var allSchem = schemaQuery.ExecuteQuery(); ...

Hi, @LaurentLam  you forgot something very important in your good practice example : the order by clause  <queryDef schema="nms:recipient" operation="select" lineCount="100"> <where> <condition expr={"[@id] > " + var.lastProcessedId} /> </where> <orderBy> <node expr="[@id]" /> </orderBy> </queryDef>...

So you have not anymore the child if you log it via a page after the process (via the debug) but when you save the content, children still present ? Have you checked the box 'Update the preloaded record' of the Storage activity ?

hmmmmm, sorry, I thought that ct.content was a DOMElement. My bad. So yes, I've just checked, delete works for xml list, I was totally wrong, forget my message I think I know where your problem is : you insert the value 'i' into the id child attribute.But i is not the value of your array(["2","1"], ...

ok Amir, this a strange thing, because the sub element 'Consommateurs' is called 'recipient'. So, when you want to access to those 'consommateurs' info, the xpath is '[recipient/recipient]' ? But it's ok, you can do it. The thing is that if you want declare indexes (with <dbindex> elements), I think...

Something strange appears on the generated schema : from the cus:recipient schema, a 'recipient' element exists into the main recipient root element, with dbIndex. It seems the extension is not well formed. Can you share the cus:recipient xml please ?

Hello Jonas, I'm not sure this is a good way to delete child elements from a XML.Can you try to user the removeChild method instead of 'delete' instruction ?Here a code but I'm not 100% sure (because iterate and delete from a list is always not simple... but as I use the element and not the index fo...

Hello Amir,Can you copy your schema extension here ? It's difficult to help without more elements. It can come from your extension, but to be sure we have so see it.Also, when you go to the nms:recipient schema edition, even if you can't edit it, you can see the generated schema (with its extensions...

This idea is really interesting.This could be related : I had a similar point : the ability to choose the sending time for each recipient, even in the same time zone. Tried to play with waves but too difficult as it's not really possible to order the messages, and finaly went to duplicate deliveries...

Here what the console send to the server to get the HTML content :<Transform xmlns='urn:ncm:publishing'> <strPublishingId xsi:type='xsd:string'>cus:Content1</strPublishingId> <strModelName xsi:type='xsd:string'>HTML</strModelName> <elemContent xsi:type='ns:Element'> <Content1 ....... xt...