PyDataSet assigned to custom not converted to dataset anymore?

Ignition
,
1

Hi, recently after upgrading to version 8.0.16 from 8.0.13 i noticed that all my tables columns were messed up.
The reason of this event apparently is that after getting a pyDataSet from system.db.runNamedQuery() and assigned it to a custom, the custom in version 8.0.13 will auto-convert it to a DataSet type, but this does not happen in 8.0.16, thus making the custom not suitable for a table.
Is this intended or is it a bug that is gonna be resolved in the next Release?

2

This is a bug, planned to be fixed in 8.0.17 and 8.1.0 (to my knowledge).

3

I noticed this as well and posted about it here:
http://forum.inductiveautomation.com/t/bug-446-runprepquery-no-longer-returning-dataset-from-script-transform-as-of-8-0-16

In the meantime you should be able cast it to a BasicDataset to retain the same functionality you had in 8.0.13.

from com.inductiveautomation.ignition.common import BasicDataset
return BasicDataset(system.db.runNamedQuery(args))
4

To add on this you could also use

return system.dataset.toDataSet(system.db.runNamedQuery(args))
5

I could have sworn I didn’t have success with that :o. I will have to try it again. Thanks!