The update operation is used to update an entity on an entity set. It typically has two records as input, one containing the entity keys of the entity one containing the values that can be updated. If a member of "Values" is set to "Not set" it is not updated at all (it is not set to null)

You also have the option to provide custom HTTP headers, if that is applicable.

With the last parameter "Break workflow on error", you can configure how the machine step will behave in the case of an error. If set to "true" - do break workflow - the machine step will stop the execution of the workflow and typically display a dialog with an error message. If set to false - do not break - it is up to the workflow designer to check the StatusCode member of the result (and/or ErrorMessage) and decided whether to abort the workflow, try again, or just ignore it.

There is usually also the option to run the operation in the context of an iterator.


The result (a record) of the operation looks like this:

  • StatusCode - the HTTP status code returned from the OData endpoint, typically 200 if the operation was successful. A value of 0 or -1 indicates a problem in the connector (i.e, no request sent to the OData endpoint)

  • ErrorMessage - has no value if the operation succeeded, otherwise a description of what when wrong

  • HasFailed - simple value containing true if operation failed

  • Entity - a record containing the values of the updated entity

  • Descriptor - is omitted by default, but if included, contains OData-related information about the entity, such as ETag

  • Headers - is omitted by default, but if included, contains all HTTP headers returned by the OData endpoint

Last updated