Symptom
"Id" is the primary key in the Job Application entity.
When a specific JobAplication ID queried, the API entity returns more than one record in the response.
Environment
Bizz, RCM Module.
Reproducing the Issue
1. Build a Boomi process by importing the Job Application SFAPI entity(Choose Query Operation)
2. Filter it based on the ID and supply the parameter(Job Applciation ID) in configurations tab of Boomi operation.
3. Run the Boomi operation and check the document count.
4. Here is the Request and Response
Request:
SELECT candidateId,candidateUsername,cust_userId,employeeId,firstName,isInternalCandidate,jobReqId,jobReqTemplateId,lastmodified,lastModifiedForAppStatus,lastName,ssn,startDate,statusId,statusItem FROM JobApplication$441 WHERE id = '8089'
Response:
#1
<JobApplication>
<id>JA$441-8089</id>
<candidateId>6803</candidateId>
<candidateUsername></candidateUsername>
<cust_userId></cust_userId>
<employeeId></employeeId>
<firstName>Test</firstName>
<isInternalCandidate>0</isInternalCandidate>
<jobReqId>12621</jobReqId>
<jobReqTemplateId>381</jobReqTemplateId>
<lastmodified>2015-09-15T11:53:58.000-04:00</lastmodified>
<lastModifiedForAppStatus>2015-09-15</lastModifiedForAppStatus>
<lastName>User2</lastName>
<ssn>014554488</ssn>
<startDate>2015-09-21</startDate>
<statusId>Hire</statusId>
<statusItem>Ready to Hire</statusItem>
</JobApplication>
#2
<JobApplication>
<id>JA$441-8089</id>
<candidateId>6803</candidateId>
<candidateUsername></candidateUsername>
<cust_userId></cust_userId>
<employeeId></employeeId>
<firstName>Test</firstName>
<isInternalCandidate>0</isInternalCandidate>
<jobReqId>12621</jobReqId>
<jobReqTemplateId>381</jobReqTemplateId>
<lastmodified>2015-09-15T11:53:58.000-04:00</lastmodified>
<lastModifiedForAppStatus>2015-09-15</lastModifiedForAppStatus>
<lastName>User2</lastName>
<ssn>014554488</ssn>
<startDate>2015-09-21</startDate>
<statusId>Hire</statusId>
<statusItem>Ready to Hire</statusItem>
</JobApplication>
#3
<JobApplication>
<id>JA$441-8089</id>
<candidateId>6803</candidateId>
<candidateUsername></candidateUsername>
<cust_userId></cust_userId>
<employeeId></employeeId>
<firstName>Test</firstName>
<isInternalCandidate>0</isInternalCandidate>
<jobReqId>12621</jobReqId>
<jobReqTemplateId>381</jobReqTemplateId>
<lastmodified>2015-09-15T11:53:58.000-04:00</lastmodified>
<lastModifiedForAppStatus>2015-09-15</lastModifiedForAppStatus>
<lastName>User2</lastName>
<ssn>014554488</ssn>
<startDate>2015-09-21</startDate>
<statusId>Hire</statusId>
<statusItem>Ready to Hire</statusItem>
</JobApplication>
#4
<JobApplication>
<id>JA$441-8089</id>
<candidateId>6803</candidateId>
<candidateUsername></candidateUsername>
<cust_userId></cust_userId>
<employeeId></employeeId>
<firstName>Test</firstName>
<isInternalCandidate>0</isInternalCandidate>
<jobReqId>12621</jobReqId>
<jobReqTemplateId>381</jobReqTemplateId>
<lastmodified>2015-09-15T11:53:58.000-04:00</lastmodified>
<lastModifiedForAppStatus>2015-09-15</lastModifiedForAppStatus>
<lastName>User2</lastName>
<ssn>014554488</ssn>
<startDate>2015-09-21</startDate>
<statusId>Hire</statusId>
<statusItem>Ready to Hire</statusItem>
</JobApplication>
Cause
In the soap request the fields statusId and statusItem are being used. These fields have foreign key relationship with underlying database table. Since the status is created in 4 locale's, soap response has 4 records
Resolution
Solution: We could filter the job application based on locale (jobAppLocale). Please use the below request to avoid duplicates:
SELECT candidateId,candidateUsername, firstName,isInternalCandidate,jobReqId,jobReqTemplateId,lastmodified,lastModifiedForAppStatus,lastName,ssn,statusId,statusItem FROM JobApplication$2314 WHERE id = '15887' and jobAppLocale='de_DE'
Note: Extra condition is added (jobAppLocale='de_DE'). As per your need please change the locale's.
Keywords
KBA , jobapplication entity duplicate records , LOD-SF-INT-RCM , RCM-Any Integration , LOD-SF-INT-BOM , Standard SF to 3rd Party Boomi Content , Problem