2173813 - Missing API entity fields in Boomi profile

Field in an API entity is missing in Boomi profile and hence we are unable to map that field in Boomi.

Boomi

A field from SuccessFactors Employee Central system has to be mapped to a third party system via Middleware Boomi. 

As shown in the image above, the requirement is to map the field called “Badge Number” to “ectint_employmentInfo_NLD_NLD_CUSTOM_VCHAR1” from the API entity "ADHOC_ectint"

However, the field “ectint_employmentInfo_NLD_NLD_CUSTOM_VCHAR1” is not visible for mapping (refer to the left-hand side of the screen).

We will first check SFAPI Data Dictionary (Navigation – Admin Tools – SFAPI Data Dictionary )to locate the respective entity and to know if the field is actually present in that entity. We find that the field is present in the entity - "ADHOC_ectint"

Now, Re-import the profile " SuccessFactors ADHOC_ectint QUERY Response" of the entity "ADHOC_ectint" in Boomi. Once the profile is re-imported, the specified field would be visible and can be mapped. This is shown below.

Open the corresponding Boomi process and launch the Connector configuration as shown below.

Re-import the profile " SuccessFactors ADHOC_ectint QUERY Response" by selecting the object as shown below and by clicking the “import” as indicated by an arrow.

Note – Boomi consultant/Implementation partner would be aware of this.

After re-importing the profile, The missing field would be visible. 

We observe that the missing field is now present and we could perform the mapping. (Highlighted Yellow)

Fields missing , unable to map , mapping problem , KBA , LOD-SF-INT , Integrations , Problem