FM2020: OpenObjectID errors occur in generated LOF (functioning links aren't being created)

Explorer ,
Jan 18, 2021

Copy link to clipboard

Copied

In FM 2020, my Book file's Generated TOC and IX files work fine, but clicking on links in the LOF displays OpenObjectID errors, and don't link to the figures in the Chapter files. Any suggestions would be greatly appreciated! 

LOF_OpenObjectID_error.png 

Views

69

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

1 Correct Answer

Adobe Community Professional , Jan 19, 2021
frameexpert Adobe Community Professional , Jan 19, 2021
Try this: edit one of the markers in the LOF and make sure that the first word is spelled with this case: openObjectId The capital "O" in Open is suspicious to me.

Likes

Translate

Translate
Jump to answer Jump to answer
Adobe Community Professional ,
Jan 18, 2021

Copy link to clipboard

Copied

Hi,

 

Do the links work in the PDF?

Did you do a MIF wash of your LOF? (Save as MIF, open the MIF and save as FM again.)

Possibly something on the reference pages of your LOF might not be correct.

There are paragraphs like this one:

openObjectId <$relfilename>:<$ObjectType> <$ObjectId>

What I would test with a backup of your files:

Create an additional LOF with the very same settings as the original one. Import paragraph formats from your old LOF into the new one. Update the book.

Then import the reference pages of this new LOF into your old one.

Delete the new LOF from the book. Update.

Test whether the links work now.

 

Best regards

 

Winfried

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Explorer ,
Jan 18, 2021

Copy link to clipboard

Copied

Hi, Winfried - 

Unfortunately, links didn't work in the .pdf. I checked the reference page content, and it appears to be identical.

I'll try a MIF wash and duplicate the LOF - thank you very much for the suggestions.

Best Regards,

Randall  

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Jan 19, 2021

Copy link to clipboard

Copied

Try this: edit one of the markers in the LOF and make sure that the first word is spelled with this case:

openObjectId

The capital "O" in Open is suspicious to me.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Explorer ,
Jan 19, 2021

Copy link to clipboard

Copied

Per your suggestion, I just edited the 1st link in the LOF, and now it works perfectly. Thank You for your sharp eyes, and for the suggestion to resolve this  frustrating issue!

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Jan 19, 2021

Copy link to clipboard

Copied

Of course, my question is why the links came out this way: OpenObjectId instead of openObjectId. If this happens when you generate the file it is definitely a bug.

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Explorer ,
Jan 19, 2021

Copy link to clipboard

Copied

Agreed - I'd tried regenerating the LOF and got the same error. Per your suggestion, I checked the Reference Page content, which displays the capitalized "O": OpenObjectId <$relfilename>:<$ObjectType> <$ObjectId>

Editing it to lowercase resolved the issue in the additional links that I've tested. Thank You, again! 
 

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Community Professional ,
Jan 19, 2021

Copy link to clipboard

Copied

Hi Randall,

 

I just tested this with FrameMaker 2020, version 16.0.1.817.

The freshly created LOF in a new book with new files had these paragraphs on the reference pages:

openXmlElementId <$relfilename>:<$UniqueXmlElementId> <$RelativeXmlElementId>
openObjectId <$relfilename>:<$ObjectType> <$ObjectId>
<$paratext> <$pagenum>

 

The spelling of the openObjectID paragraph starts with a lower case o. Correct. And the links work.

 

I do not know whether this was different in 16.0.0.

What's your version (Help | About)?

Please update, when you do not have 16.0.1.

 

Best regards

 

Winfried

 

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Ran_techwriter AUTHOR LATEST
Explorer ,
Jan 19, 2021

Copy link to clipboard

Copied

Hi, Winfried -

Thank you for testing in FrameMaker 2020, version 16.0.1.817 (this is the version I'm currently running, too). I'm not sure whether the reference page text formatting was different in the previous version, but I'm happy to know that your test output also produced functioning links. This particular project file utilized a previously-created LOF to streamline LOF formatting, so the faulty format may have been imported from that file. Thanks to frameexpert's sharp eyes, I recognize what to look for in the event that this issue occurs in future FM projects.

 

Best Regards,

Randall    

Likes

Translate

Translate

Report

Report
Reply
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more