# Component Error in changing table value

**URL:** <https://forum.inductiveautomation.com/t/component-error-in-changing-table-value/101281>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [January 23, 2025, 11:56am UTC](https://forum.inductiveautomation.com/t/component-error-in-changing-table-value/101281 "2025-01-23T11:56:00Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Senthee\_Wu](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/senthee_wu/32/67770_2.png) [@Senthee\_Wu](https://forum.inductiveautomation.com/u/Senthee_Wu)\
**Post date:** [January 23, 2025, 11:56am UTC](https://forum.inductiveautomation.com/t/component-error-in-changing-table-value/101281/1 "2025-01-23T11:56:00Z")

</div>

Hello,  
I'm getting an error when I change a table value.  
This error triggers irregularly  
As in the following gif：  
 ![img_v3_02iq_d344ec61-2902-4289-a608-aac35b3f1f1g](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/c/9ca6d4afe1dded31c708c644dbedcf34a4304744.gif)

Can you please tell me what is the problem with this  
Here are my components and data：

> **Data1**
>
> ```python
> [
> {
> "ItemCode": "01",
> "ItemValue": 25
> },
> {
> "ItemCode": "02",
> "ItemValue": 24
> },
> {
> "ItemCode": "03",
> "ItemValue": 25
> },
> {
> "ItemCode": "04",
> "ItemValue": 26
> },
> {
> "ItemCode": "05",
> "ItemValue": 25
> },
> {
> "ItemCode": "06",
> "ItemValue": 25
> },
> {
> "ItemCode": "07",
> "ItemValue": 24
> },
> {
> "ItemCode": "08",
> "ItemValue": 25
> },
> {
> "ItemCode": "09",
> "ItemValue": 26
> },
> {
> "ItemCode": "10",
> "ItemValue": 25
> }
> ]
> 
> ```

> **Data2**
>
> ```python
> [
> {
> "ItemCode": "01",
> "ItemValue": 25
> },
> {
> "ItemCode": "02",
> "ItemValue": 25
> },
> {
> "ItemCode": "03",
> "ItemValue": 25
> },
> {
> "ItemCode": "04",
> "ItemValue": 25
> },
> {
> "ItemCode": "05",
> "ItemValue": 26
> },
> {
> "ItemCode": "06",
> "ItemValue": 26
> },
> {
> "ItemCode": "07",
> "ItemValue": 26
> },
> {
> "ItemCode": "08",
> "ItemValue": 24
> },
> {
> "ItemCode": "09",
> "ItemValue": 24
> },
> {
> "ItemCode": "10",
> "ItemValue": 24
> }
> ]
> 
> ```

---

<div class="post-metadata">

**Author:** ![Senthee\_Wu](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/senthee_wu/32/67770_2.png) [@Senthee\_Wu](https://forum.inductiveautomation.com/u/Senthee_Wu)\
**Post date:** [January 23, 2025, 12:00pm UTC](https://forum.inductiveautomation.com/t/component-error-in-changing-table-value/101281/2 "2025-01-23T12:00:48Z")

</div>

Component is too long ,that cann`t be sent.  
Here is the json.  
[Components.json](https://forum.inductiveautomation.com/uploads/short-url/bbB2C0Lpz7OsMT86Nz85dkXTf01.json) (59.5 KB)

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [January 23, 2025, 12:54pm UTC](https://forum.inductiveautomation.com/t/component-error-in-changing-table-value/101281/3 "2025-01-23T12:54:53Z")

</div>

What's the warning message in the red triangle beside PROPS?

---

<div class="post-metadata">

**Author:** ![Senthee\_Wu](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/senthee_wu/32/67770_2.png) [@Senthee\_Wu](https://forum.inductiveautomation.com/u/Senthee_Wu)\
**Post date:** [January 23, 2025, 12:58pm UTC](https://forum.inductiveautomation.com/t/component-error-in-changing-table-value/101281/4 "2025-01-23T12:58:02Z")

</div>

![img_v3_02iq_9e67a48b-e2de-4a96-9615-7c824ae5146g](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/7/577a8d5d38f62f9e81f75439dc56e368dcda3ac3.jpeg)

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [January 23, 2025, 1:42pm UTC](https://forum.inductiveautomation.com/t/component-error-in-changing-table-value/101281/5 "2025-01-23T13:42:22Z")

</div>

It's weird! The error message is pointing to the problem. By changing to,  
`yAxes.0.appearance.grid.dashArray : 5 5`  
rather than your value of 10 the problem seems to resolve.

I have no idea why it works for one set of data and not the other.

> SVG dashed array. The pattern of dashes and gaps used to paint the stroke. It's a list of comma separated lengths (in pixels) and percentages (percentage of the total stroke length) that specify the lengths of alternating dashes and gaps. If an odd number of values is provided, then the list of values is repeated to yield an even number of values. Thus, "5,3,2" is equivalent to "5,3,2,5,3,2". (See [yAxes.appearance.grid](https://docs.inductiveautomation.com/docs/8.1/appendix/components/perspective-components/perspective-chart-palette/perspective-xy-chart#yaxesappearancegrid).)

Congratulations on posting all the information needed to reproduce the problem! Some folks make us drag it out of them.

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [January 23, 2025, 2:21pm UTC](https://forum.inductiveautomation.com/t/component-error-in-changing-table-value/101281/6 "2025-01-23T14:21:03Z")

</div>

Regarding the coding: I would be inclined to create a custom property on the root of the view to keep track of whether 1C or 2C is selected. Then just bind the color properties of each button to that custom prop. It avoids all the getSibling hoo-haa.

I'd also use [Perspective Built-In Themes | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/ignition-modules/perspective/styles/perspective-built-in-themes#built-in-theme-colors) rather than hard code them into the app. It's then very easy to be consistent and to modify the whole application in one place.
