AF Elements reference across AF Databases
Customer would like to be able to use AF Data References to reference AF Elements that reside in different AF Databases. This would allow him to not have to replicate elements and attributes across multiple databases.
Alistair Frith commented
I'm not sure that this is possible. I think the original questioner wanted \\AFServer\DB1\ElementA to be a reference to AFServer\DB2\ElementA and for all the attributes of ElementA on DB2, along with all its child elements and their attributes, to be available in DB1 as if they had been defined there.
As Patrice has suggested, this would need a new type of weak reference, basically saying 'link to location x in this other AF hierarchy'. I don't think this is what Stephen is describing.
Patrice Thivierge-Fortin commented
@Steve:How about a new type of Element. e.g. a Foreight weak reference element that would be read-only in the database that is importing it. What you explained works for an attribute, but not for an element. I think this would be handy for customers so they could build their databases in a Separation of Concerns manner (Soc). e.g. Physical assets DB, Visualization DB with the first levels hierachy that would be built so user can easily find hist assets, and the last levels would be the Assets from the physical assets DB. That would add another level of Genericity that would make our system even more powerful. Hope you liked my .02 cents :)
This is possible with the currently shipping product via the use of StringBuilder data reference. You can construct a configuration string that points to elements/attribute in a different database - i.e. construct the full path to the desired element/attribute using the StringBuilder DR.