# XY Chart Component Error

**URL:** <https://forum.inductiveautomation.com/t/xy-chart-component-error/51468>\
**Category:** Ignition\
**Created:** [September 29, 2021, 8:27pm UTC](https://forum.inductiveautomation.com/t/xy-chart-component-error/51468 "2021-09-29T20:27:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nicholas.robinson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nicholas.robinson/32/22188_2.png) [@nicholas.robinson](https://forum.inductiveautomation.com/u/nicholas.robinson)\
**Post date:** [September 29, 2021, 8:27pm UTC](https://forum.inductiveautomation.com/t/xy-chart-component-error/51468/1 "2021-09-29T20:27:54Z")

</div>

Looking around I can see several topics about the XY chart, example:

> [@\[BUG-2363\] XY Chart - Component Error since 8.1.4](https://forum.inductiveautomation.com/t/bug-2363-xy-chart-component-error-since-8-1-4/45394/9):
>
> 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

We are using 8.1.10 and we see this happening:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/6/469b67a83871402287a3db4d5ed6072dd3db0a16.png)

In order to fix it, I click F5 to refresh the browser and it goes away.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/c/6cc85742a3914d466c9020aa90ee58c6e50be7d2.png)

It seems to occur randomly.

We feed the chart from a pre generated dataset tag like this:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/0/707ec60bef0a6369bdfc01752d603dbfc12a40bb.png)

Is there anything we can do to prevent this or any know fixes that are in the pipeline already?

Thanks,

Nick
