Tc Create And Update Multi
This Snap create multiple objects of any Teamcenter element of type item or derived types, such as document, part, design or ME Process. The Snap is processing the data input and can automatically call Teamcenter update for those attributes, which are not able to be processed with the create input definition in Teamcenter.
The Multi Snap allows to create multiple items from a single document and uses as few API calls as possible to improve overall performance.
Supported Accounts
- This is a Write-type Snap.
Works in Ultra Tasks

Prerequisites
- A valid Teamcenter account with the required permissions.
Snap views
| Type | Description | Examples of upstream and downstream Snaps |
|---|---|---|
| Input |
This Snap has exactly one document input view. The required input of the snap is an array of objects including object type nad attributes for each object that needs to be created in Teamcenter. |
|
| Output |
This Snap has exactly one document output view. The output of the snap is a JSON array “result” including as much objects as should be created. Each JSON object includes two objects, one for the Item created and one for the Item Revision created. |
|
| Learn more about Error handling. | ||
Examples
Tc Create And Update Multi: Simple create of five objectsSnap settings
| Field/Field set | Description |
|---|---|
Label
String |
Specify a unique name for the Snap. Modify this to
be more appropriate, especially if there are more than one of the same Snap in the
pipeline.
Default value: Tc Create And Update Multi |
Configure policy
Checkbox |
Select this checkbox to run the Snap with a specific named Teamcenter policy. A policy determines the set of object properties that Teamcenter returns. Learn more: Configure policy. Default status: Deselected |
Configure session context
Checkbox |
Select this checkbox to run the Snap with a group, role, or project other than the one configured in the account. Learn more: Configure session context. Default status: Deselected |
Objects Path
String/Expression |
Specify the JSON array object containing objects to be created/updated in Teamcenter. In JSON document the content for path can look like this:
Default value: N/A Example: $.objects |
Map displayed to internal values
Checkbox/Expression |
Allows to disable mapping of display to internal mapping. Disabling will improve performance. This is relevant for references or LOVs. ON: Values given in input are displays and will be mapped to internal values for attribute. OFF: No mapping of attribute values. Input document contains internal value for attribute itself. Default value: Deselected Example: Deselected |
Handle localized properties
Checkbox/Expression |
In case input document contains localized properties as an object turn this checkbox ON. Result objects will contain an JSON object In case no localization properties are in content of input document leave checkbox OFF to avoid a loss of performance. Input could look like this:
Localization attribute has to exist in Teamcenter. Property “xyz_localised_test” is a customized attribute and will not ootb be in another Teamcenter. Default value: Deselected Example: Deselected |
Try set multi localized properties call
Checkbox/Expression |
OFF: Each properties is set by own API call. ON: All properties are set by a single API call as a multi call. Default value: Deselected Example: Deselected |
Always include log
Checkbox/Expression |
OFF: No log information. ON: Configure Setting to add log information to output next to resulting
Default value: Deselected Example: Deselected |
Configure error handling
Checkbox |
Select this checkbox to define how the Snap behaves when Teamcenter returns an error. Use these settings for analysis and debugging. Learn more: Configure error handling. Default status: Deselected |
Simplified expand
Checkbox |
Select this checkbox to make the Snap look for the name given in
Expand Attributes Path in the input document (for example,
When deselected, configure Expand Attributes Path as a string or an expression. Default status: Deselected |
Expand Attributes Path
String/Expression |
Specify the JSON path to the expand attributes in the input document. Expand attributes are the list of attributes that the Teamcenter response must contain. Each name must be the technical name of a valid property in the Teamcenter data model for the expected objects. For example:
Learn more: Configuring Expand Attributes. Default value: N/A Example: $.expandAttributes |
Build reference/lov documents
Dropdown list/Expression |
Select how the Snap represents references and lists of values (LOVs) that
Teamcenter returns. The Snap can return them as nested JSON objects instead of
flattened IDs and internal values with additional
The available options are:
Default value: Use Default Example: Yes |
Configure output
Checkbox |
Select this checkbox to specify the Teamcenter properties that the Snap includes in the output. This Snap offers the output settings described in Variant: type and reference related fields for suggestion. Default status: Deselected |
Snap execution
Dropdown list |
Choose one of the three modes in
which the Snap executes. Available options are:
|