Cross-Reference provides a table to view all object references within the solution. This data powers the Find Results Panel and enables impact analysis before changes.
Access: Track Changes → Cross-Reference
Parent Page: Track Changes Tools (Reference)
Table Columns
| Column | Description |
|---|---|
| ID | Unique reference identifier |
| ObjectName | Referenced object name |
| UsedByTable | Table using the object |
| TableItem | Specific item referencing object |
| Location | Exact location in system |
Usage Patterns
The Cross-Reference table is typically accessed indirectly through:
- Find Results Panel (easier interface)
- Use Count calculations
- Unused Objects detection
Limitations - Indirect References
Not Detected
Cross-Reference cannot detect indirect usage:
| Type | Example | Risk |
|---|---|---|
| String References | Asset("/folder1/tag1") | Hidden dependencies |
| Link Properties | TagReference via string | Broken on rename |
| Script Strings | Dynamic tag names | Runtime errors |
| .NET Methods | Toolkit string access | Functionality loss |
| External Access | OPC UA, MQTT, APIs | External system failure |
Best Practice
When possible, use direct references:
- Use
Tag1.GetName()instead of"Tag1" - Reference objects directly in scripts
- Document any indirect usage
Navigation
Double-click any row to navigate to the usage location in Designer.
Warning
The Find Results panel, Use Count, and Unused Objects all rely on Cross-Reference data. Objects used indirectly will not appear in these tools. Verify carefully before deleting or renaming objects.
See Also
- Track Changes Tools (Reference) - Parent section
- Find Results Panel (Reference) - Search interface
- Use Count (Reference) - Usage frequency
- Unused Objects (Reference) - Cleanup tool
In this section:
The root page V10:@parent could not be found in space v10.