🚀 go-pugleaf

The Structure Guide states that one can create an element with an attribute of type UniqueID and allow the user to enter a value for the UniqueID attribute, as opposed to letting Frame do it on the fly. The Guide also states that within a book, the value of this UniqueID has to be unique.

I am creating a rather generic file that will be used in several books. In each book, I want a cross-reference within the generic file to target a particular element in one of the files in the book; let this file be FileA. So, within FileA I have an element with its uniqueID attribute set to TheAttribute. THere is a cross-reference in the generic file that targets this element.

Now, in another file FileB in another book, I have a similar element whose uniqueID attribute also has the value TheAttribute.

So, if I update the book containing FileB and the generic file, the cross-reference in the generic file still targets the element in FileA, even though FileA is not part of the second book and is not open. Furthermore, if I put FileA and FileB and the generic file in the SAME book and update it, the cross-reference still targets the element in FileA, even though the book has two files each with an element containing the SAME value of the uniqueID; that is, in this case, the uniqueID is not really unique.

So, what is going on? I am unable to do what the Structure Guide seems to imply that I can do. Is there something else I have to do? I have tried setting the Id reference attribute in the cross-reference to NOT read-only and then setting its value manually, but Frame makes me go through the cross-reference dialog box to set the value.

Obviously, Frame is recording the file name along with the value of the uniqueID, but that all seems contrary what the Structure Guide states.

I can get around this using conditional text but would like to avoid it.

Thanks,
Van