Thank you. These steps worked.

And I did end up having to submit a technical support ticket, so I'm hoping this gets resolved as soon as possible since this is on our Production server and has stopped work now for two weeks.

FMPS 2020.2 is what we are using to generate PDFs.   However, at this time, no map is generating a PDF using FMPS, whether it has a GUID name or word-based name. 

The Title field would primarily be used for the repository view. Any searches conducted would be searches on content within the file or for a specific GUID.   Yes, a custom metadata field that wouldn't be changed would resolve this. Would we also be able to view this custom field in the repository v...

We had the same issue with AEM Guides and using FMPS to generate the PDF, whereas the DITA-OT did not allow draft comments to appear. Here is the answer we received from Mayank Mehrota at Adobe:   - - - The option to suppress <draft-comment> from PDF output is available via 'ConditionalizeComment' i...

Up until last week, my maps with GUID names had been publishing to PDF just fine.   As of this week, all maps with GUID names fail. The only way to get the map to generate an output is to recreate the map in AEM Guides, then copy all content. Doing this creates a map with a name in the Name field, i...

Thank you. We'll try this.   However, right now, all my attempts to generate any PDF from any GUID map is failing. I'll be posting this as a separate question.

We'd like to retain a different Title because the <title> element inside the file is what displays in the output (for example, Features), but the title in the repository needs to be more descriptive (for example, Features - Product X) so that we do not end up with a dozen files titled Features in th...

Done. An email was sent that included the dita file with the Thai content. I was going to also include the PDF output, but for some odd reason, maps that generated a PDF output last week just fine are failing this week.

We're using FMPS 2020.2  and Arial