# \[BUG-2363\] XY Chart - Component Error since 8.1.4

**URL:** <https://forum.inductiveautomation.com/t/bug-2363-xy-chart-component-error-since-8-1-4/45394>\
**Category:** Ignition\
**Created:** [April 8, 2021, 3:48pm UTC](https://forum.inductiveautomation.com/t/bug-2363-xy-chart-component-error-since-8-1-4/45394 "2021-04-08T15:48:53Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![ShaneH](https://avatars.discourse-cdn.com/v4/letter/s/3e96dc/32.png) [@ShaneH](https://forum.inductiveautomation.com/u/ShaneH)\
**Post date:** [June 4, 2021, 3:23pm UTC](https://forum.inductiveautomation.com/t/bug-2363-xy-chart-component-error-since-8-1-4/45394/9 "2021-06-04T15:23:51Z")

</div>

I’ve found that “pushing” the data to the dataSources property of the XY Chart seems to help.

That is, instead of putting a binding on the dataSources property that “pulls” the data in, I created a custom property that has a transform script to create the data and data structure, and then as a last step of the script does something like:

self.getChild(“XYChart”).props.dataSources.myData = myData

It’s a work around for sure, but seems to help with the spurious component errors.

HTH.  
-Shane

---

_[View the full topic](https://forum.inductiveautomation.com/t/bug-2363-xy-chart-component-error-since-8-1-4/45394)._