TN - IT09112609 - Duplicate or Deleted Scripts Appear in an InTouch Application

• Document Version: 001
• Applies to Version(s): AVEVA InTouch 2017 + 

Description  

Duplicated scripts in an InTouch application may be caused by stale or corrupted script metadata files. Rebuilding the application metadata and script index files can resolve the duplication.

For InTouch 2023 and later, rebuild the metadata and .json files, including ScriptsInfo.json and WindowsInfo.json.

For versions earlier than 2023, rebuild the metadata and OrgHeir.xml file.

This procedure applies to both Managed InTouch applications and Stand-alone InTouch applications.

Symptoms

A user may see one or more of the following symptoms in WindowMaker:

• Scripts appear duplicated.
• Script lists show repeated entries.
• Previously deleted scripts reappear in the application.

Quick Tip
For InTouch versions prior to 2023, simply deleting OrgHeir.xml, opening WindowMaker, and then closing it again is often sufficient to regenerate the file. For Managed applications, remove OrgHeir.xml from both the CheckedIn and CheckedOut folders.

If duplicate scripts persist, follow the complete rebuild procedure below.

Solution Steps:

For Managed InTouch applications, the issue may exist in either the CheckedIn or CheckedOut copy of the application. Both locations must be cleaned.

Step 1: Backup the application. 

Before making any changes, back up the entire InTouch application. This allows you to restore the application if the rebuild does not resolve the issue or causes unexpected behavior. 

Step 2: Close WindowMaker

Close WindowMaker before making any changes.

Step 3: Delete the contents of the Metadata folder(s)

Managed  InTouch Applications

C:\Program Files (x86)\ArchestrA\Framework\FileRepository\GalaxyName\ObjectFileStorage\<InTouchApplicationName>\CheckedIn\Metadata

C:\Program Files {x86)\ArchestrA\Framework\FileRepository\GalaxyName\ObjectFileStorage\<InTouchApplicationName>\CheckedOut\Metadata

Stand-alone InTouch Applications

Perform the same procedure using the applications local Metadata folder

The default location is:

C:\Users\Public\Wonderware\Intouch Applications\<InTouchApplicationName>\Metadata

Step 4: Delete the Metadata Index Files 

For InTouch 2023 and later

Delete the following files from the InTouch application folder:

• ScriptsInfo.json
• WindowsInfo.json

For InTouch versions prior to 2023

Delete: 

• OrgHeir.xml

For Managed InTouch applications, delete these files from both the CheckedIn and CheckedOut application folders.

Step 5: Run the Cross-Reference utility. 

Open WindowMaker and navigate to:

 Tag Dictionary → Cross Reference

Step 6: Wait for the rebuild to complete

The rebuild process can take several hours for a larger application. 

Step 7: Rebuild the Script Index

After the Cross Reference completes:

• Click each script type (Application, Keys, Condition, etc.).
• Open one script from each category.
• Click the ... button to display the full script list.

This causes the metadata files (ScriptsInfo.json, WindowsInfo.json, or OrgHeir.xml depending on the InTouch version) to be regenerated.

AVEVA has documented that duplicated scripts can occur after certain application migrations or when the script metadata becomes corrupted. Rebuilding the metadata forces WindowMaker to regenerate its script index from the application contents.