# Ixon MQTT Evaluation: Convert data structure into a more usable format

**URL:** <https://forum.inductiveautomation.com/t/ixon-mqtt-evaluation-convert-data-structure-into-a-more-usable-format/95024>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [August 22, 2024, 5:41pm UTC](https://forum.inductiveautomation.com/t/ixon-mqtt-evaluation-convert-data-structure-into-a-more-usable-format/95024 "2024-08-22T17:41:26Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\
**Post date:** [August 22, 2024, 5:51pm UTC](https://forum.inductiveautomation.com/t/ixon-mqtt-evaluation-convert-data-structure-into-a-more-usable-format/95024/3 "2024-08-22T17:51:53Z")

</div>

Yes, I am. The data is coming from an Ixon router, which supports Sparkplug B; however, it was not being parsed correctly on Cirrus Link's side (no tags displayed). Something about google protobufs, so I tried straight JSON format.

If the Sparkplug format would handle the structure better, as you suggested, I will switch back and debug it further with Cirrus Link's support.

---

_[View the full topic](https://forum.inductiveautomation.com/t/ixon-mqtt-evaluation-convert-data-structure-into-a-more-usable-format/95024)._