troubleshooting topic validation error after saved as book with FM component

[Andy38108926n5yf]

The troubleshooting topic alone passed validation check, but it fails after I saved it as a book. Is there something I can do to fix this? 

Moreover, the [title] of [cause] tag gets the proper subheading format, but after saved as a book that [title] would be formatted as title.0 instead.

Are these two problems related somehow?

FM 17 on Windows 11.

[Matt-Tech Comm Tools]

I believe troubleshooting is a DITA 2.0 topic type.

What version of DITA are set up to use right now?

[Andy38108926n5yf]

Hi Matt,

thank you for the response.

I was very excited when I resumed to work with FrameMaker, mostly because of DITA 1.3 and the new troubleshooting topic.

I am currently composing and migrating the documentation into XML DITA 1.3, FM 17.

The console error mentioned something about missing ID, even though the topic has been assigned a random unique ID.

As for DITA 2.0, from what I read it's still quite a while before we could work with it.

Getting Out of Trouble: DITA 1.3 Troubleshooting – DITA Writer

[Matt-Tech Comm Tools]

Ah, I didn't recall the troubleshooting being DITA 1.3.

Check your setup...I'm betting you are using DITA 1.2.

Set it to DITA 1.3 and you should be in business. If that doesn't work, reach out to Adobe directly at tcssup@adobe.com

[Andy38108926n5yf]

Thank you, Matt. 
Let me re-confirm which DITA I'm currently use and get back to you asap.

edit:

Structure > DITA Options says I'm on DITA 1.3.

Task topic also says 1.3.

Book components, all points to 1.3.

[Matt-Tech Comm Tools]

It sounds like the bookmap EDD isn't supporting something that the ditamap EDD is supporting.

Please reach out to Adobe at tcssup@adobe.com to evaluate.

[Andy38108926n5yf]

Good morning, Matt.

I'm pretty sure I have re-installed a clean FM 17 environment after my initial experiment with EDD. In the earlier attempt, I experimented to duplicate the EDD of every DITA 1.3 topic, mostly for layout purposes. But now I have managed those within DITA output templates, I reinstalled FM 17 and use the defaults EDD.

I've sent the support yesterday, and yet to get their response.

Thank you,

Andy

[frameexpert]

Andy, do you have time for a quick web meeting? I can suggest a solution. Please contact me offlist: rick at frameexpert dot com

[Andy38108926n5yf]

Good morning, Rick.

Thank you for responding to my thread. It's currently working hour for me, so let me email your asap for that web call.

Regards,

Andy

[frameexpert]

Here is an unedited video that explains a solution. Note that in the video, I open the wrong output template instead of ditabase.template.fm, but the results would be the same.

https://youtu.be/Z5yDU0Ib5tY

[Andy38108926n5yf]

The video is most welcome, Rick. 

edit: come to think of it, I should've supplied my problematic XML files - I never thought you'd go ahead and actually did an experiment recreating my issue. Thank you for the trouble.

[Andy38108926n5yf]

I've checked out your recording. Thank you again.

1. Looks like the simplest way to fix my problem is to remove the ditabase1.3 reference, and point it to ditabase instead.

CompositeDocTemplate_1.2=ditabase.template.fm
CompositeDocTemplate_1.3=ditabase.template.fm

2. If I follow your direction and modify the template directory, I lose all of my customized layout for the DITA output.

3. The result looks good now, but the main book still has red NONAME element.

fixed troubleshooting structure view

 

main book structure view

4. I will continue to publish solely on ditabase template now, and will report back if I found any issues after I ditch ditabase1.3 template.

 

Regards,

Andy

[Matt-Tech Comm Tools]

Yes, awesome recording from Rick!

He chose one of two paths to get your validation issue resolved, and likely chose the "swap output template method" because most folks haven't customized their default output template.

If you've already customized the output template, instead you might want to update the EDD in your modified template. 

Save a copy of your modified template file and import your element definitions from your valid Troubleshooting file to test.

Sorry I can't record a bright shiny video for you this morning to demonstrate!  🙂

I'm sure Rick will chime in soon as well.

[Andy38108926n5yf]

Good morning, Matt. 

Thank you for the follow-up explanation and suggestion. 

I am still confused about EDD, how to properly read and write them, or how to incorporate them into my customized templates and FM's default EDD. It would be very much appreciated if you could offer a brief explanation of it.

Currently, I only customized the master pages of the DITA output template for the layout's visual.

Regards,

Andy

[Matt-Tech Comm Tools]

Take a look at Adobe's documentation or my EDD workbook for details on modifying your structure environment.

However, it sounds like your template mods are minor, and that you could follow Rick's suggestion to get your DITA to validate, and then import the master pages (or otherwise modify the "new" template) to get the output you need.

Rick or I are available to help you if you need to go beyond what we can write up here.