In some scenarios, creating a linked table to an internal AF table is more appropriate than linking to an external table. For example, an internal AF table which contains a list of assets and their associated tag name may be applicable to multiple AF databases on an AF Server. This hypothetical table data could be used in a template strategy that leverages a table lookup and substitution parameters to populate a PI Point data references.
As it stands, the internal table must be export, or copied, from one AF database to another and any future table updates require the same. The internal table is self-contained within PI AF and storing the data within an external table, like SQL, is redundant. Allowing for internal AF tables to be linked from other AF Databases would allow for easy replication and eliminate potential update errors over time.
