Importing Stakeholders is slightly different than the other SuperOffice entities. This is because strictly speaking it is not a real entity. It is a link between Sale, Company and Person.
When you have details of a Sale, Company and a Person in one line in the import file, you can make this person a stakeholder. To do so you have to at least link one field of the Stakeholder fields. But what if you don’t have such a value in your source to link any of the Stakeholder fields to?
The -Helper- field comes in handy here. If the source does not have the Comment or the Sales Role field then use any field -which might be added via a Static Field transformation– and map that to field to
-Helper-. This field has no function except to tell DataBridge: this is a stakeholder.
Example with a stakeholder field in the source
Let’s look at an example where the source does contain details about the stakeholder. In this case the Sales Role is in the source file.
The field mapping would look like the example below.
Example without a stakeholder field in the source
Now, let’s take an example file that does not have any specific stakeholder details.
In this case, a transformation that adds a field without a value is used to create a ‘dummy column’ so the -Helper- field can be mapped.
The helper mapping makes sure there is a link between the sale, company and the person and will create a stakeholder.
Deduplication
Stakeholders can never be duplicated. This means that a single person can’t be in the list of stakeholders of the same sale more than once. Such options can also not be found in the deduplication settings in DataBridge.
Tip: process only a few lines of the source is a safe way to test the integration.