We would like to upload Userdata using the SFAPI but not with the Standard-Proxy-to-SOAP Scenario.
We need to read a CSV-File (from different HR-systems) and upload the data using the SFSF or OData Adapter.
For this, we already have a working Operationmapping and a SFSF-Receiver Channel.
But now I figured out, that we need to change some processing parameter for the User Upsert.
Those are the parameters:
Those parameters are also defined in the WSDL:
<urn:upsert>
<urn:type>User</urn:type>
<!--1 or more repetitions:-->
<urn:sfobject>
...
</urn:sfobject>
<!--Zero or more repetitions:-->
<urn:processingParam>
<urn:name>?</urn:name>
<urn:value>?</urn:value>
</urn:processingParam>
</urn:upsert>
But the SFSF-SOAP-Adapter does not take it!
If you just put it into your output structure the SFSF-Receiver creates something terribly wrong:
<upsert xmlns="urn:sfobject.sfapi.successfactors.com">
<type>User</type>
<sfobject>
<type>User</type>
<status>active</status>
<externalId>...</externalId>
<username>...</username>
</sfobject>
<sfobject>
<type>User</type>
<name>defaultPassword</name>
<value>RANDOM_PWD</value>
</sfobject>
</upsert>
...
--> Has anyone ever tried to do this???
I know, you need to generate the datatypes with eclipse. But the Eclipse Add-On does not offer any options for this.
I also recognized, that when using the ODATA API, you can use "API option profiles" which you can create in SF to set the options.
But the ODATA Adapter does not send the URL-Parameter to the SFAPI if you enter it in the channel - So this isn't usable either.
In the meantime we opened a OSS-call a few weeks ago...