# Ignition Re-Certification & Expiring Certifications 2025

**URL:** <https://forum.inductiveautomation.com/t/ignition-re-certification-expiring-certifications-2025/106201>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [May 13, 2025, 4:58pm UTC](https://forum.inductiveautomation.com/t/ignition-re-certification-expiring-certifications-2025/106201 "2025-05-13T16:58:30Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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 1, 2025, 3:01pm UTC](https://forum.inductiveautomation.com/t/ignition-re-certification-expiring-certifications-2025/106201/7 "2025-06-01T15:01:59Z")

</div>

> [@michael.flagler](#):
>
> couldn't find a way to script nested datasets

_Psssst!_

> [@Report with Scripted Nested Data](https://forum.inductiveautomation.com/t/report-with-scripted-nested-data/11801):
>
> The report datasource scripting examples explain how to access the nested data in another key for use constructing a custom dataset. What I don’t see is how to construct nested data that would be suitable for use with a child table in a table group. I have a parent dataset that I’m constructing via script due to annoying limitations of an ancient SQL Server 2000 instance. I need a subquery for each row that could be done with a normal query, but there’s no way to add a regular subquery to a s…

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-re-certification-expiring-certifications-2025/106201)._
