cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

CompoundEmployee API, SuccessFactors - steps.extractvariables.ExecutionFailed

brandonbollin
Active Participant

on ‎2021 Dec 02 7:41 PM

0 Kudos
2,261

Getting an error when trying to execute the CompoundEmployee API via Postman. The error code isn't anywhere in SAP documentation so I don't know what it's trying to tell me. Has anyone seen this before and can point me in the right direction?

I know the authorization is good as it works in my IDM implementation to pull down the data. Just can't understand why I can't pull down data via Postman to review the raw response that IDM sees. Thanks.

Know the answer?

Help others by sharing your knowledge.

Answer

Need more details?

Request clarification before answering.

Show replies
Show replies
Waeltken
Explorer
‎2024 Jan 01 4:24 PM
0 Kudos

What was the resolution on this item? We are experiencing the same issue.

brandonbollin
Active Participant
‎2024 Jan 02 2:14 PM
0 Kudos

waeltken Turns out I was passing my login ID and company ID incorrectly. That's what ExtractCompanyId was referring to. Check your authorization settings and make 100% sure your credentials are correct.

Waeltken
Explorer
‎2024 Jan 07 6:08 AM
0 Kudos

thank you - did you have to first run a separate login operation. My understanding is that it is supposed to be a separate call where the authentication details are passed in the Body of the request instead of being passed in the authentication header in Postman. Here's what the body would look like (see below)

When you fixed your call, did you have to first run a login call like this or are you passing the user/password in an authentication header directly in the Query call? Even with this separate login operation I'm still getting the same error. Our companyId is definitely correct. "Failed to execute the ExtractVariables: ExtractCompanyId" 

<soapenv:Envelope> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn: sfobject.sfapi.successfactors.com">" <br>    <soapenv:Header/><br>    <soapenv:Body><br>        <urn:login><br>            <urn:credential><br>                <urn:companyId>COMPANY</urn:companyId><br>                <urn:username>USER</urn:username><br>                <urn:password>PASSWORD</urn:password><br>                <!--Optional:--><br>                <urn:developerKey>?</urn:developerKey><br>            </urn:credential><br>            <!--Zero or more repetitions:--><br>            <urn:param><br>                <urn:name>?</urn:name><br>                <urn:value>?</urn:value><br>            </urn:param><br>        </urn:login><br>    </soapenv:Body><br></soapenv:Envelope>
brandonbollin
Active Participant
‎2024 Jan 08 2:08 PM
0 Kudos

Here's what I have for my initial login API call:

<Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/">
    <Body>
        <login xmlns="urn:sfobject.sfapi.successfactors.com">
            <credential>
                <companyId>YourCompanyID</companyId>
                <username>YourServiceAccount</username>
                <password>{{PROD-PWD}}</password>
            </credential>
        </login>
    </Body>
</Envelope>

I also have a header set on that call, Content-Type=text/xml; charset="utf-8". I don't know if that matters or not but I have it set and it works so, might as well mention it.

I also have a basic authorization header with the username@companyID and password base64 encoded so we're essentially passing the login info in both the body and header. I set it up that way as that's what I remember SAP documentation saying it needed. I don't honestly know if that's necessary but I know it works so I'm not changing it.

For the CompoundEmployee call, I have the same two headers mentioned above set the same way, Authorization and Content-Type, and this is my XML body:

<Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/">
    <Body>
        <query xmlns="urn:sfobject.sfapi.successfactors.com">
            <queryString>SELECT person,
                personal_information,
                address_information,
                email_information,
                phone_information,
                employment_information,
                job_information,SecondaryAssignments
                FROM CompoundEmployee
                <!--WHERE last_modified_on > to_datetime('2023-10-30T11:10:00Z')-->
                WHERE person_id_external = '60003141'
                <!--WHERE person_id = '53810'-->
            </queryString>
            <param>
                <name>maxRows</name>
                <value>800</value>
            </param>
        </query>
    </Body>
</Envelope>

This is what works for me. As you can see, I have some lines commented out that I can uncomment as needed but you get the gist. Again, this is what is working for me. Your results might vary. If you can't get it to work as I've set it up, not sure what else to tell you. I'm actually an IDM developer / architect so I just pieced this together through documentation and trial & error.

Accepted Solutions (0)

Answers (0)

Ask a Question