OpenText Connector 26.3
OpenText Connector Help

# Update Node Metadata

To update the metadata of a node in Extended ECM, you can use the connector's update action. You must supply some XML that specifies the metadata to update.

By default, you can update the generic fields listed by the ApiFieldName configuration parameter. If you want to update a generic field that isn't listed, you must set ApiFieldName, ApiFieldType, and SourceFieldName, replacing the default values of those parameters with new values that include the additional field(s).

The following is example XML that you could supply in the `IdentifiersXML` parameter of your update action. This would update the generic `description` field:

    <IdentifiersXML>
      <identifier value="AUTN_IDENTIFIER_OF_DOCUMENT_TO_UPDATE">
        <xmlmetadata>
          <description>The new description</description>
        </xmlmetadata>
      </identifier>
    </IdentifiersXML>

The following XML demonstrates how to add one or more supplemental markings to a document in Extended ECM:

    <IdentifiersXML>
      <identifier value="AUTN_IDENTIFIER_OF_DOCUMENT_TO_UPDATE">
        <xmlmetadata>
          <supplementalmarking>MARKING_TO_ADD</supplementalmarking>
          <supplementalmarking>ANOTHER_MARKING_TO_ADD</supplementalmarking>
        </xmlmetadata>
      </identifier>
    </IdentifiersXML>

Extended ECM also supports custom fields that belong to categories. When the connector synchronizes with Extended ECM it adds categories to the Knowledge Discovery document metadata. You can use the update action to update the values of these fields. Specify the new values in the same format as the Knowledge Discovery document created by the connector.

For example, you might supply the following XML in the `IdentifiersXML` parameter of your update action, to update two custom fields that belong to a category:

    <IdentifiersXML>
      <identifier value="AUTN_IDENTIFIER_OF_DOCUMENT_TO_UPDATE">
        <xmlmetadata>
          <categories>
            <_2074355_2/>
            <_2074355_3>NEW FIELD VALUE</_2074355_3>
          </categories>
        </xmlmetadata>
      </identifier>
    </IdentifiersXML>

TIP: In Knowledge Discovery documents, the category names are prefixed with an underscore. This underscore is to ensure that the XML is valid and is not part of the category name. The initial underscore is discarded when the connector performs the update.

## Update a Summary

Some Extended ECM systems use Knowledge Discovery to generate AI summaries of documents and rich media files. The OpenText Connector can update nodes in Extended ECM with new summaries. For example:

    <IdentifiersXML>
      <identifier value="AUTN_IDENTIFIER_OF_DOCUMENT_TO_UPDATE">
        <xmlmetadata>
          <summary>
             <source>Knowledge Discovery</source>
             <value>A new node summary</value>
          </summary>
        </xmlmetadata>
      </identifier>
    </IdentifiersXML>

The value from the metadata field `/summary/source` is used to populate the Extended ECM summary source, and `/summary/value` is used to populate the summary text.

Copyright 2026 Open Text
Version 26.3 | Last updated July 2026

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery OpenText Connector 26.3

Topic Title: Update Node Metadata