# Automation Professionals' Integration Toolkit Module

**URL:** <https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934>\
**Category:** 3rd Party Modules\
**Tags:** perspective, ignition81, vision, scripting, ignition83\
**Created:** [June 13, 2023, 12:42am UTC](https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934 "2023-06-13T00:42:35Z")\
**Posts on this page:** 1\
**Showing post:** 153

<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:** [August 13, 2024, 8:44pm UTC](https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934/153 "2024-08-13T20:44:38Z")

</div>

New ~~beta~~ _production_ release: [v2.0.18.242262035](https://www.automation-pros.com/ignition/Integration%20Toolkit-2.0.18.242262035-v81.modl)

Added a new expression function: [parsePath()](https://www.automation-pros.com/toolkit/doc/datasets.html#parsepath)

This function accepts a tag path or qualified path in string format and produces a dataset with the various qualified components broken out. If necessary, additional strings may be supplied, and the result dataset will have a row for each.

(I've been frustrated with the need for scripts to produce proper historical paths from simple tag paths.)

I'm using this with a client right now, so will likely be declared production grade soon.

---

_[View the full topic](https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934)._