Thank you for your reply. Tried DITA2Trisoft. The file was converted, but was not imported because of the following error. Tried looking up this error, but came back empty handed.

Thank you for your reply. Tried DITA2Trisoft. The file was converted, but was not imported because of the following error. Tried looking up this error, but came back empty handed.

Dear all,

Huntley is indeed on the correct route to resolve the issue. My take is that your CCMS has the Topic Type property defined as a mandatory property. Hence you need to supply a value for it during the import stage. This is also the reason why this error does not come up on environments which have this property defined as optional.

You can supply this value indeed as Huntley suggested through the filemap.xml which is available in the folder with your GUID-ized content.

You should check the ishfields structure for your topics to see whether there is a structure as shown below present

<ishfield name="FMODULETYPE" level="logical">Any value applicable in your CCMS from you list of values</ishfield>

If not you have to add this to each and any of the ishfields structures defined for the topics. You can easily find them by looking at the ISHType attribute on the ishobject element surrounding the ishfields element. The topics are marked as ISHModule. So search for all ishobject tags having the ISHType attribute set to ISHModule and add or correct the ishfield tag as shown above in the bolded section.

It might be that you have other properties defined as mandatory as well and need to supply them in a similar approach in order to provide the correct value(s) for them.

I hope this helps,

Kind Regards,

Raf

Dear Raf and Huntley,

Thank you for your replies. I searched the .3sish files that I found in a directory that XMetal uses to store local versions of topics, but didn't find an ishfield entry for "Topic type". Not sure what to do. Let me provide more details about what I am trying to do. I need to document hundreds of commands. One option is to manually create the topics for the commands in Publication Manager and then check out the topics and add the content. This approach works, but it is time-consuming.  A better option for me is to use a script to extract the information about the commands (syntax, description, ...) from the specs and automatically create the command topics. To do so, I opened a sample command topic in XMetal and used the topic's XML content to create the following template that I can use to automatically create new XML files. The template does not include the ids and the script that I created to generate new command topics does not generate GUIDs. One thing to mention here is that DITA2Trisoft complained about the ids not being there for the reference and title elements, so I ended up adding two dummy ids to get DITA2Trisfot to accept the file.

My script populates the template and spits out an XML file for every command. The challenge now is importing the XML files into Publication Manager. I know that the template works because if I check out a command topic, switch to Plain Text View, replace the content of the topic with the template's content, and check in the topic, the check-in operation completes without a problem, even though the template didn't have any GUIDs defined. When I check out the topic again and switch to Plain Text View, I can see that GUIDs were added by Publication Manager where needed, as shown here.

However, when using DITA2Trisoft to import a file generated by my script, the import operation fails with the error shown in an earlier post. I looked at the following .3sish file for the topic created from the template, but I didn't see an ishfield element for Topic type.

The following is what is contained in the filemap.xml. 

Not sure where to go from here

Best regards.

Dear Persimmon,

The .3sish files are files used by the authoring bridge and they do not contain all of the properties which are assigned to the object in the CCMS.

I would suggest the following steps with respect to the process you described above and which should resolve your issue.

1/ Check through the webclient or the property dialog windows of either Publication Manager/Authoring Bridge which properties are marked mandatory for topics.

You can easily identify them by the * which is available after the label of the field or by trying to upload one of the topics (or a dummy topic) through the webclient while you provide as little information as needed. The dialogs (first for the logical level, second the version level and last the language level dialog) will error on missing mandatory properties.

My guess is that the 'Topic Type' property is marked as mandatory.

Do choose one value from the drop down which you will apply in the filename for each and every topic available.

2/ Just before you start the 'Import' step of the DITA2Trisoft application, you need to extend the filemap.xml file with the property for the 'Topic Type' property with the choose value from step 1.

eg. <ishfield name="FMODULETYPE" level="logical">Your choosen value</ishfield>

So each object should have an structure similar to the one shown below:

3/ After you have added all the missing mandatory properties for you object (you can leave out the status and language as these are automatically added), you can import the content into the CCMS.

I hope this helps.

Kind Regards,

Raf

Dear Raf,

I searched the DITA2Trisoft, the SDL LiveContent 2014 website, and the web for examples or information on how to "run an XSL transformation against the filemap.xml file" so that the FMODULETYPE files is present in the filemap.xml file instead of having to manually add an FMODULETYPE entry for every .xml file to import, but I could not. 

Note: I found a topic about the sample DITA2Trisoft.xsl file. I customized a copy of the file to add the FMODULETYPE field. It worked. I can now import files with out having to manually add FMODULETYPE entries. Many thanks for your help.

This is what the DITA2Trisoft documentation says about the filemap.xml file.

Overview of the filemap.xml file