Hi Will,
So this appears to be by design. Per our developers answer:
=========
Given the way the user set up the metadata in the thread (which is a key repro step), here's what's going on. This is By Design, I think.
The Linked Schema is set up with only ListB published, not ListA.
The user set up the metadata to reference folder Main directly.
Therefore, when viewing the ListB in Display as a Guest, you don't have permission to see Main and therefore don't.
If you change the metadata to not reference Main, well, nobody can see A1, since you're still looking at the Lists schema (which would be in Display) ListA cannot be found. If you take away the reference to the Lists schema, it's looking in the same schema, which is the linked schema, and ListA cannot be found.
If you now add ListA to the linked schema, and the metadata is like this:
<tables xmlns="
http://labkey.org/data/xml">
<table tableName="ListB" tableDbType="NOT_IN_DB">
<columns>
<column columnName="Foo">
<fk>
<fkColumnName>Key</fkColumnName>
<fkTable>ListA</fkTable>
<fkDisplayColumnName>Name</fkDisplayColumnName>
</fk>
</column>
</columns>
</table>
</tables>
Then it works. In this case the FK references the same (linked) schema and ListA is published there, and the guest user has permission for the Display folder, so it works.
=========
Regards,
Jon