Home › Forums › DITA and XMetaL Discussion › Reuse a single row from a large table in a different topic? Author Enterprise 9 › Reply To: Reuse a single row from a large table in a different topic? Author Enterprise 9
Reply to: Reuse a single row from a large table in a different topic? Author Enterprise 9June 28, 2017 at 7:03 pm
The functionality that drives the DITA authoring is effectively disabled in Plain Text view because the APIs required are not available.
You can easily conref to a row from another table just like you can any other element in Tags On or Normal view:
1. Put your selection inside the table you want to add the conref target row to.
2. From the Reuse menu select “Insert Element with Content Reference”.
3. In the dialog that appears (Insert Element with Content Reference) you will see a list of id values under “Start of Range” that are in the current document.
a. If the row you want to conref to is in the list select it then click OK. A source row (“local content”) will be inserted and the reference to the other row will be added to it (the conref attribute will be set).
b. If the table row is in another document then select the other file using the Browse button. A list of elements that have an id in that other document will be shown and you can select the row from this list. A source row (“local content”) will be inserted and the reference to the other row will be added to it (the conref attribute will be set).
In both cases the source (aka: local content) for the row that is inserted will be given the same number of entry elements as the row above it in the table (the same as adding a row “normally”). This allows it to be rendered as part of the rest of the table even in cases where you have selected a row with fewer or more entry elements. The number of entry elements isn't mandated by XML validity, or DITA, or the CALS table specs. In most cases you'll want to conref to similar table rows to keep things simple and avoid working with complicated structures that include spanning (@morerows, @namest and @nameend).
If this doesn't work for you I would suggest contacting SDL to ask for special instructions. Their integration with XMetaL Author Enterprise might alter our features, or their CMS might have special requirements for this.