Business Integration Solutions documentation

How to: Set up a Code Event / NETCode Event

A Code Event or NETCode Event triggers an outbound pipeline based on AL code in Microsoft Dynamics Business Central.

To trigger a code event, create AL code that triggers the right code. See How to: Create a Code Event.

To set up a Code Event:

  1. Create a connection and insert the element CODEEVENT.
  2. On the elements line, select Edit.
  3. On the Code Event Setup page, fill in the following fields:
Field Description
Event ID The identifier to trigger this specific code event.
Table ID The code event triggers with a record scope. The table ID specifies which record this event shares.
Table Filter Optionally, enter a table filter to execute this code event only with records in a specific range.
Post with job queue Enable this option to run the connection asynchronously from the session triggering the code event, using a separate job queue entry.
Job Queue Category Code Set the job queue category code to ensure parallel processing.
  1. Select Check Configuration to see if there are any configuration errors.
  2. Select OK.

Code Event Setup (SaaS)

To set up a NETCode Event:

  1. Create a connection and insert the element NETCODEEVENT.
  2. On the elements line, select Edit.
  3. On the NETCode Event Setup page, fill in the following fields:
Field Description
Object Type Select the BC object type to trigger the pipeline.
Object ID Specify the specific BC object ID.
Object Name Specifies the object name (selected automatically).
Table No. Select the table on which to apply filters.
Table Filter Specify the table filter. This filter applies to the data set.
Post With Job Queue Select this field to process the connection using the job queue with a specific category.
Job Queue Category Code Select the job queue category used for grouping and filtering jobs.
  1. Select Check Configuration to see if there are any configuration errors.
  2. Select OK.

NETCode Event Setup

The NETCode Event is available only for on-premise environments and is marked as obsolete. Consider switching to the Code Event in your connections.