# Dataset Parameters into Report's Table

**URL:** <https://forum.inductiveautomation.com/t/dataset-parameters-into-reports-table/85590>\
**Category:** Ignition\
**Tags:** ignition81, reporting\
**Created:** [February 12, 2024, 9:03pm UTC](https://forum.inductiveautomation.com/t/dataset-parameters-into-reports-table/85590 "2024-02-12T21:03:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Colin\_Quinn](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@Colin\_Quinn](https://forum.inductiveautomation.com/u/Colin_Quinn)\
**Post date:** [February 12, 2024, 9:03pm UTC](https://forum.inductiveautomation.com/t/dataset-parameters-into-reports-table/85590/1 "2024-02-12T21:03:37Z")

</div>

Hello,

I am trying to build a table within a perspective report based on a query I am running outside of the report. Here are the parameters I am passing in to the report, where `report_info` is the results of a named query.

```auto
reportParams = {
	    "complete_date": datetime.datetime.now(),
	    "picklist_id": some_id,
	    "requestor": some_id.requestor,
	    "job_num": some_id.job_number,
	    "request_date": some_id.due_date,
	    "picked_by": some_id.picked_by,
	    "table_data": report_info
	}

```

which is being taken in to the data source as follows where the `table_data` parameter is set to dataset:

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

I have tried a few variations of filling a table with the `pick_data` key and even the original `table_data` dataset without any luck. I would assume I can access the data with some variation of what is in the property inspector as well as `@pick_data.description@`:

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

I have been unable to find any genuine documentation on the dataset parameter type, so even a point in the right direction would be appreciated. Thanks in advance.

---

<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:** [February 12, 2024, 9:16pm UTC](https://forum.inductiveautomation.com/t/dataset-parameters-into-reports-table/85590/2 "2024-02-12T21:16:28Z")

</div>

I expect you will need to start with a query data source in the report as a template for design purposes (as only those present themselves in the UI), and later replace that data key with the scripted or parameterized one.

Also note that whatever column names you use in your design, you will have to make the substitute data sources conform. You cannot use dynamic column names in a report's design.

{Also, I adjusted the topic. It has nothing to do with Perspective.}

---

<div class="post-metadata">

**Author:** ![Colin\_Quinn](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@Colin\_Quinn](https://forum.inductiveautomation.com/u/Colin_Quinn)\
**Post date:** [February 12, 2024, 9:21pm UTC](https://forum.inductiveautomation.com/t/dataset-parameters-into-reports-table/85590/3 "2024-02-12T21:21:59Z")

</div>

I am trying to avoid using a query data source. The reason being that I am trying to report on table rows that are no longer available, so I am querying for the data, manipulating it, and _then_ sending this report with `executeAndDistribute`.

---

<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:** [February 12, 2024, 9:24pm UTC](https://forum.inductiveautomation.com/t/dataset-parameters-into-reports-table/85590/4 "2024-02-12T21:24:15Z")

</div>

> [@Colin\_Quinn](#):
>
> avoid using a query data source

I understand, but you need one to be a dummy for **design**. After you get the dummy data from a true query to look right, delete the dummy and use that data key in your script to assign the true data.