# Auto-Export all Vision window Documentation

**URL:** <https://forum.inductiveautomation.com/t/auto-export-all-vision-window-documentation/72643>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [April 19, 2023, 1:33pm UTC](https://forum.inductiveautomation.com/t/auto-export-all-vision-window-documentation/72643 "2023-04-19T13:33:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![danFromNj](https://avatars.discourse-cdn.com/v4/letter/d/76d3ee/32.png) [@danFromNj](https://forum.inductiveautomation.com/u/danFromNj)\
**Post date:** [April 19, 2023, 1:33pm UTC](https://forum.inductiveautomation.com/t/auto-export-all-vision-window-documentation/72643/1 "2023-04-19T13:33:18Z")

</div>

Is there a way to access a Vision Window's "Documentation" via scripting? We are using the "Documentation" feature in the project browser to create detailed notes and change logs for a customer. When we release a new version of the software, we would like to be able to export all window/template documentation to a csv so that we can use it to easily create a Software Update document for the customer.

My preferred method would be through scripting. I tried grabbing the window object in the script console and searched it to see if there was a getDocumentation function attached to the object. No luck!! Is there any way to access this via scripting? If not, is there another method that can be used generate a csv? Going through and copying/pasting the documentation for every screen/template in the project is too tedious of a process to do regularly.

Thanks  
Dan

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [April 19, 2023, 4:15pm UTC](https://forum.inductiveautomation.com/t/auto-export-all-vision-window-documentation/72643/2 "2023-04-19T16:15:07Z")

</div>

With [Ignition Extensions](https://forum.inductiveautomation.com/t/ignition-extensions-convenience-utilities-for-advanced-users/64615) installed, you could call `system.project.getProject()` to get an instance of the [`Project`](https://files.inductiveautomation.com/sdk/javadoc/ignition81/8.1.26/com/inductiveautomation/ignition/common/project/Project.html) Java class. From there, call `getResourcesOfType` with a resource type of `com.inductiveautomation.factorypmi.common.VisionModule.WINDOW_RESOURCE` (this'll only work directly in the designer; doing it from the gateway scope will be a bit trickier).

That will give you a list of `ProjectResource`s, which have a [`getDocumentation`](https://files.inductiveautomation.com/sdk/javadoc/ignition81/8.1.26/com/inductiveautomation/ignition/common/project/resource/ProjectResource.html#getDocumentation()) method.

Technically, Ignition Extensions is not required (you can access the project through other scripting means) but it's the easiest entrypoint.