Delete column from pie chart

Ignition
1

I’m using a Pie chart, which should read 2 historical tags. And in your dataset I’m using TagHistory to get the 2 tags.

image
image1259×901 269 KB

The problem is that when the application goes to runtime, it also takes the column “_tstamp” and overlays the other values.
If I cancel the dataset, it returns again when the application is started again.

image

Is there a way to cancel this _tstamp column, or some property not to show in the graph?

Thanks!!

2

Move your history binding to a custom property of type dataset.
Change the data property’s binding to an expression binding, and use the columnRearrange function (ignore the name) to filter out the t_stamp column.

3

Hi PGriffith , thanks for your attemption!
This part worked, but now it takes 4 readings and the first row, in column A, appears blank, I tried some scripts in the graphics to delete just that row, rowindex 0, but it deletes everything, or it deletes the others and this one stays. Do you have any idea? Thanks again

image
image983×545 42.3 KB

4

We’ll need to see your scripts in order to see if you missed something in there.

5

Hi , sorry for the delay…

I did like this:
1o. ( Custom Properties - like said @PGriffith )

image
image1273×599 67.8 KB

2o ( where do i get the values from the table)

image
image1478×791 90.5 KB

3o ( original DataSet)

image
image1489×790 68.1 KB

image
image1184×494 31.3 KB

4o ( to delete the first row)

image
image1247×725 63.8 KB

6

Hi how are you? Any idea for this step above? Thank you!!

7
  1. I don’t believe you need to import system here.
  2. Your variable, myList is actually a dataset. I would be careful with the naming.
  3. self.data and event.source.parent.getComponent('PieChart3').data are references to the same property. I would use self.data
  4. A dataset does not have a selectedIndex. I would expect the script to fail here.
  5. system.dataset.deleteRow() takes an Integer argument for the rowIndex, you have supplied it with a List. It "might" be smart enough to do a conversion, but I wouldn’t count on it.
  6. Your configureChart extension function is writing to the Data property, but you also have a binding on that property. So any changes you made in the configureChart function I would expect get overwritten by the binding.

You don’t need the script. You only need the bindings as @PGriffith suggested.

The tag history binding on the Dataset2 custom property, and the expression binding on the Data property.

If you do that and you’re still missing one data point, then I would make sure that nothing else is writing to the data property.

8

Hi , you are right! I deleted the scripts , and did just the 2nd dataSet like told PGriffith. But I must change something, see below . Thanks for help.

image
image1064×710 167 KB

9

I don’t think you have followed @PGriffith’s advice closely enough. This looks as though you have a Tag History Binding on the Data property of the PieChart.

  1. Create a custom property of type dataset. It can be on the Pie Chart or the Root Container, doesn’t really matter.
  2. Add a Tag History Binding to the custom property with whatever settings you want.
  3. Add an expression binding to the Data property of the Pie Chart using the columnRearrange expression function to filter out the t_stamp column, and populate the Pie Chart.
10

Yes, that’s exactly what I did. and in the TAgHistory property of the DAtaset2 I configured it according to the printscreen and in the original Data of the Chart I used the ColumnRearrange,tks