Use the Create step to add new object instances. For example, if you work with an Account object, you can use the Create step to add a new account.
The Create step name can contain only alphanumeric characters, underscores (_), spaces, and Unicode characters.
The following image shows a Create step for the Account object:
To create new objects:
Choose the
Input Fields
tab and select all the fields that you will be adding to the object. Some are required; others are optional.
For each field name, set its source to one of the following values:
Content
,
Field
, or
Formula
.
You can also add an object by using the
Auto Map
option. For example, if you want to create an Account object in Salesforce, you can select the Salesforce connection and account object on the
Create
tab and select
Auto Map
on the
Input Fields
tab.
Click the
+
icon and select multiple fields simultaneously to automap them.
Application Integration matches the best possible fields based on the field names and assign as the input fields. Informatica does not guarantee exact field matches. After the fields are mapped, you must manually verify if the mappings are correct and update as needed.
In the modern view, when you import a project from an attachment and the process includes an output field named
Created Account
, the Create step also adds another output field named
Created Account
. Therefore, the process displays two
Created Account
fields in the modern view. You can ignore the duplication because it does not cause any issue with the process. In the classic view, only one
Created Account
field appears.
Using Reference Fields
Note that:
If you do not include a reference field on the
Input Fields
tab for the object you are creating, Process Designer uses the value of the current object at runtime.
Reference fields for the
Applies To
object are set if they are not set explicitly in the Input tab.
When the content of a reference field is set to empty, it is not included in the create statement. (This prevents problems that might occur when explicitly setting a field to empty or null could violate data constraints.)