# self.getSibling("Table").props.data

**URL:** <https://forum.inductiveautomation.com/t/self-getsibling-table-props-data/60888>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [June 17, 2022, 2:48pm UTC](https://forum.inductiveautomation.com/t/self-getsibling-table-props-data/60888 "2022-06-17T14:48:01Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew.Meronek](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@Andrew.Meronek](https://forum.inductiveautomation.com/u/Andrew.Meronek)\
**Post date:** [June 17, 2022, 2:48pm UTC](https://forum.inductiveautomation.com/t/self-getsibling-table-props-data/60888/1 "2022-06-17T14:48:01Z")

</div>

Given the following as an onActionPerformed action for a Perspective PB:

def runAction(self, event):  
“”"  
This event is fired when the ‘action’ of the component occurs.

```
Arguments:
	self: A reference to the component that is invoking this function.
	event: An empty event object.
"""
data = self.getSibling("Table").props.data
Excel_xlsx = system.dataset.toExcel(True,[data])
system.perspective.download("table_export.xlsx",Excel_xlsx)

```

Is there a known issue with self.getSibling(etc.).props.data? Specifically, the data in question has a python script doing a transform that adds a column to data that comes from a query binding, in JSON format. I have a bunch of table/button combos where this works that do not include an added script transform, but I have one case where the Excel export doesn’t work, and a difference is that this one case is the only table that includes a transform script. Is this a known bug/thing?

If I view the data in the table or copy the data into Notepad to view the post-transform JSON, it all looks fine.

---

<div class="post-metadata">

**Author:** ![kvane](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kvane/32/22228_2.png) [@kvane](https://forum.inductiveautomation.com/u/kvane)\
**Post date:** [June 17, 2022, 5:24pm UTC](https://forum.inductiveautomation.com/t/self-getsibling-table-props-data/60888/2 "2022-06-17T17:24:08Z")

</div>

The [system.dataset.toExcel()](https://docs.inductiveautomation.com/display/DOC81/system.dataset.toExcel) function expects a dataset for the “dataset” Parameter. Are you sure the Table component’s data prop is currently a [dataset](https://docs.inductiveautomation.com/display/DOC81/Datasets)? You may be able to change the format the query that populates the table returns in.

Or you may need to loop through the table’s object and generate a dataset using this function: [system.dataset.toDataSet - Ignition User Manual 8.1 - Ignition Documentation](https://docs.inductiveautomation.com/display/DOC81/system.dataset.toDataSet)

It would look somewhat like this simple example that assumes there is a dataset of 1 column called “id”:

```
data = self.getSibling("Table").props.data
#make list of headers for dataset
headers = ['id']
#generate empty list for dataset
dataset = []
#loop through table object and build a new row from the data
for row in data:
	newRow = [row["id"]]
	dataset.append(newRow)
#generate dataset
dataset = system.dataset.toDataSet(headers, dataset)
Excel_xlsx = system.dataset.toExcel(True,[dataset])
system.perspective.download("table_export.xlsx",Excel_xlsx)
```

---

<div class="post-metadata">

**Author:** ![Andrew.Meronek](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@Andrew.Meronek](https://forum.inductiveautomation.com/u/Andrew.Meronek)\
**Post date:** [June 17, 2022, 7:30pm UTC](https://forum.inductiveautomation.com/t/self-getsibling-table-props-data/60888/3 "2022-06-17T19:30:09Z")

</div>

That makes sense, I overlooked the requirement for system.dataset.toExcel(). Thanks. Following this down, given:

```
def getList(x):
	return x.keys()
headers = getList(value[0]) 

rows = []
for x in value:
	rows.append(list(x.values()))

newDataset = system.dataset.toDataSet(headers, rows)

return newDataset

```

This is adding the data transform as a specific “transform” step instead of putting it in the script for exporting to excel. This seems to work for some tables but not all - with a KeyError:21 at the line with system.dataset.toDataSet(). I’m not sure what the problem is; the number of headers and number of rows _seem_ to match up, but it’s easy to miss as this error is popping up in a rather large set of data that’s not easy to eyeball.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [June 18, 2022, 4:15pm UTC](https://forum.inductiveautomation.com/t/self-getsibling-table-props-data/60888/4 "2022-06-18T16:15:48Z")

</div>

Consider moving the actual query binding to a custom property, as a dataset, then perform your transform on a property binding to the table’s `props.data`. Then your script can access the original dataset for export.

---

<div class="post-metadata">

**Author:** ![Andrew.Meronek](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@Andrew.Meronek](https://forum.inductiveautomation.com/u/Andrew.Meronek)\
**Post date:** [June 20, 2022, 3:48pm UTC](https://forum.inductiveautomation.com/t/self-getsibling-table-props-data/60888/5 "2022-06-20T15:48:09Z")

</div>

I need to export the altered data with the added column, not the original query.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [June 20, 2022, 4:41pm UTC](https://forum.inductiveautomation.com/t/self-getsibling-table-props-data/60888/6 "2022-06-20T16:41:30Z")

</div>

Then use two custom properties. The first with the query binding, the second with the column added (but still a dataset). The the table’s data binding looks at the second custom property to transform to satisfy all the json table configuration requirements.

---

<div class="post-metadata">

**Author:** ![Andrew.Meronek](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@Andrew.Meronek](https://forum.inductiveautomation.com/u/Andrew.Meronek)\
**Post date:** [June 20, 2022, 4:52pm UTC](https://forum.inductiveautomation.com/t/self-getsibling-table-props-data/60888/7 "2022-06-20T16:52:29Z")

</div>

We got it to work; we found a rare circumstance in our column creation script that caused it to not generate a field for a particular row.