We were able to import dita files with conref's to reusable content in ver 13 but with upgrade we lost that functionality. Support couldn't resolve it telling it is by design. Is there anyone who experience similar problem and interested to learn about their workarounds?
Our solution: We are removing the conrefs from the topics and redoing the conrefs after the import. This will add extra cycle time.
There is a setting in %LOCALAPPDATA%\SDL\InfoShare Client\14\Trisoft.ContentImporter.config
(or %LOCALAPPDATA%\RWS... if you have an RWS folder instead of SDL)
<validateReferences>Warning</validateReferences>
that is supposed to cause unresolved references to create a warning rather than failing to import. That might fix the problem.
For example, we use:
<processors>
<dita>
<ditasettings>
<addFormatAttributeToReferences>false</addFormatAttributeToReferences>
<addLanguageAttributeToRoot>true</addLanguageAttributeToRoot>
<addScopeWhenExternalReference>true</addScopeWhenExternalReference>
<convertConditions>true</convertConditions>
<convertDocumentTypes>false</convertDocumentTypes>
<validateReferences>Warning</validateReferences>
</ditasettings>
</dita>
</processors>
<trisoft.contentimporter.settings>
<dita>
<addFormatAttributeToReferences>false</addFormatAttributeToReferences>
<addLanguageAttributeToRoot>true</addLanguageAttributeToRoot>
<addScopeWhenExternalReference>true</addScopeWhenExternalReference>
<convertConditions>true</convertConditions>
<convertDocumentTypes>false</convertDocumentTypes>
<validateReferences>Warning</validateReferences>
</dita>
</trisoft.contentimporter.settings>
That was the first thing we tried with Support team’s recommendation but it didn’t work.
That was the first thing we tried with Support team’s recommendation but it didn’t work.
Translate
