Setting Up Publisher Objects

Dynamics CRM 4.x only This topic only applies to the publisher for Microsoft Dynamics CRM 4.x.

The publisher objects tell the Dynamics CRM 4.x server which objects to publish messages for and what to include in the message.

If your schema file has duplicate nodes, you receive the following error message when you try to create a DTS with an XML connection: Invalid Schema or document: Node list not unique.

See Creating Schemas With Duplicate Entity/Parent/Child Names for more information.

To Set Up Publisher Objects

  1. In the Console, expand Integration Server and click Publishers and Bridges node. The Publishers/Bridges screen appears.
  2. Select a publisher object and click Properties.
  3. Open Step 4 Publisher/Bridge Properties.
  4. If you are manually configuring the publisher settings, click Add, Modify, and Delete to select and configure a published object. The Publisher Entry dialog box appears.
  5. Configure the Dynamics CRM Object. Select the object you want to configure for publication:
    Note:  
    • If you are implementing a pre-built template, the object list may be automatically configured.
    • Both label settings support the substitution variables listed in the dialog box.
    • Events — Check which events you want detected for publication.
    • Message Label — Type a label to use when the message is written to the message queue. This label can be used by a queue integration process to filter the messages for processing.
    • InsightLabel Attribute — Optionally, type a label to be added to the XML message as an attribute called InsightLabel attached to the root node. This label can be used:
      • By a queue integration process to filter messages for processing.
      • In a link in the Workbench.
    • Retrieve Entire Object — Check if you want the publisher to query the Dynamics CRM 4.x server when the message is processed so that all information is returned. By default, the Microsoft Microsoft Dynamics CRM 4.x Publisher includes only the data in the message that has been updated.
    • Include Parent Object — Select a parent object if you want the publisher to fetch a related parent record and include the data in the XML message.
    • Include Child Objects — Select a child object if you want the publisher to fetch all of the related child records and include the data in the XML message.

      Note: If you include parent or child objects in your message and fields exist in the included objects with the same name, the generated schema file assumes the fields are all of the same type. If the fields are not of the same type, unexpected results may occur when processing the field values.

    • Process Only If — Select to specify settings to instruct the publisher how to filter the published messages.
    • Ignore Changes From — Ignore any changes made by the selected user. Changes made by the ignore user are not placed into the ScribeIn message queue. This is an object-level filter. A similar setting in Step 4 Publisher/Bridge Properties is a global setting affecting all published objects on the Dynamics CRM 4.x server.

      This is useful to avoid sending changes in an endless loop between your Dynamics CRM 4.x application and other applications, or to avoid sending unimportant changes made by a special process or administrator.

      • If you are implementing a pre-built template, the object list may have been automatically configured.If you are implementing a pre-built template, the object list may have been automatically configured.
  6. Click OK.
  7. In Step 4 Publisher/Bridge Properties, click XML Schemas. TIBCO generates the new XML schema, which is required when you connect to the XML schemas using the Workbench XML Source Connection Wizard.
  8. Browse to where you want save the schema files and click OK. You are prompted to verify the location, or locations.
  9. Click OK.

Next step

See also

Publisher For Microsoft Dynamics 365

Substitution Variables For Dynamics CRM 4.x