# Can a MySQL Connector Lookup create a new node in XML?

**URL:** <https://community.cdata.com/t/can-a-mysql-connector-lookup-create-a-new-node-in-xml/569>\
**Category:** CData Arc\
**Tags:** question, cdata-arc, lookup\
**Created:** [December 14, 2023, 5:59pm UTC](https://community.cdata.com/t/can-a-mysql-connector-lookup-create-a-new-node-in-xml/569 "2023-12-14T17:59:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![russell-jerseypost](https://avatars.discourse-cdn.com/v4/letter/r/439d5e/32.png) [@russell-jerseypost](https://community.cdata.com/u/russell-jerseypost)\
**Post date:** [December 14, 2023, 5:59pm UTC](https://community.cdata.com/t/can-a-mysql-connector-lookup-create-a-new-node-in-xml/569/1 "2023-12-14T17:59:36Z")

</div>

My lookup looks like this

 ![076dfedc-a1d8-4078-9d26-d5ae871b6def.png](https://us1.discourse-cdn.com/cdata/original/1X/d8942e1d4fcb11c2cb9c34837b3f2b01e45f3ca4.png)

`/I **tems/tracking\_events/parcel** ` node does not exist. Only&nbsp;/I **tems/tracking\_events** exists

When I run the connector I don’t get a parcel or a barcode node.

I have also tried&nbsp;/I **tems/tracking\_events/parcel\_barcode.**

Does the XML node have to exist in the incoming message?

I can extract the barcode to a message header okay.

---

<div class="post-metadata">

**Author:** ![James\_B](https://sea3.discourse-cdn.com/cdata/user_avatar/community.cdata.com/james_b/32/1688_2.png) [@James\_B](https://community.cdata.com/u/James_B)\
**Post date:** [December 14, 2023, 8:29pm UTC](https://community.cdata.com/t/can-a-mysql-connector-lookup-create-a-new-node-in-xml/569/2 "2023-12-14T20:29:27Z")

</div>

You’re using an earlier version of the Lookup connector here - in the latest release of the Lookup connector from the 23.3 release of CData Arc at&nbsp;[https://arc.cdata.com/support/builds/](https://arc.cdata.com/support/builds/)&nbsp;you’ll find that the Lookup feature has been revamped, and you can declare a parent folder for the new elements to be added to:

 ![bfb26125-6dfc-40c5-974b-cdef9c921bda.png](https://us1.discourse-cdn.com/cdata/original/1X/ddc8296a3ada730d5144b2c65e772e15ab2a7c57.png)

This even has a test button that you can use to try it out:

 ![5d86879b-9e6e-40c0-8e01-34452c5879ce.png](https://us1.discourse-cdn.com/cdata/original/1X/ade4c5dbaeb7ee71e00458cf9e3ce502671a93fc.png)

The version that you’re on is a little simpler, just allowing you to output a sibling element, so&nbsp; **/Items/tracking\_events/parcel\_barcode** &nbsp;should have worked - what were you seeing when you did that?

---

<div class="post-metadata">

**Author:** ![russell-jerseypost](https://avatars.discourse-cdn.com/v4/letter/r/439d5e/32.png) [@russell-jerseypost](https://community.cdata.com/u/russell-jerseypost)\
**Post date:** [December 15, 2023, 10:01am UTC](https://community.cdata.com/t/can-a-mysql-connector-lookup-create-a-new-node-in-xml/569/3 "2023-12-15T10:01:41Z")

</div>

Okay, I think I have more info on&nbsp;23.0.8517.0

- Using a destination of **/Items/parcel\_barcode** works. A new node is created
- **/Items/thing/parcel\_barcode** did not create a new node ‘thing’ or&nbsp;subnode **parcel\_barcode**. **thing** doesn’t exist in the original XML.
- **/Items/tracking\_events/parcel\_barcode** gives a ‘Success’ result but the parcel\_barcode node is not added to the existing&nbsp; **/Items/tracking\_events**.

In the meantime we&nbsp;&nbsp;will upgrade to the latest version