Method description

replacePerson is the method used to create or replace a single person in itslearning. This is a destructive write-over of all of the original information. See more info below.

Preconditions for use


Message Schema

Input parameters / request message elements



Data type

Allowed values



The syncID of the person to be replaced


Max 64 chars



The Person data to be stored in the new record. See docs full details on the person object



Please refer to the WSDL for the full element structure, only key elements are described here

Response message elements



Data type


Empty response element



You must provide the request with all mandatory fields for a person, not only the fields you want to update, as the method will overwrite all of the fields that can be provided with a replacePerson request. See list below of fields that will be overwritten and fields that will be kept if the user already exists.
If the syncID does not exist in itslearning, the person with the syncId will be created instead.



I want to insert or update a person in itslearning - I have not kept track of whether it already exists or not.

Example request message

<soapenv:Envelope xmlns:soapenv="" xmlns:ims="" xmlns:ims1="" xmlns:ims2="" xmlns:ims3="">
<ims3:formatName xsi:nil="true" xmlns:xsi=""/>
<ims2:email>[email protected]</ims2:email>
<ims3:street>First street3</ims3:street>
<ims3:street>Second street3</ims3:street>

Example response message

<s:Envelope xmlns:s="" xmlns:u="">
<text>Object did not exist, has been inserted instead</text>
<o:Security s:mustUnderstand="1">
<u:Timestamp u:Id="_0">

Fields that will be overwritten

If user exists and following fields are not provided in the replacePerson request, fields will be set to 0/NULL/Empty.

  • Prefix

  • Voice

  • Mobil

  • Street[0]

  • Street[1]

  • Postcode

  • Locality

  • BDay

  • Extension fields

    • CustomString fields

    • Email account information

    • Cloud account information (cloud account will be disabled if cloud account was imported)

    • IsExternalUser

    • PrivacyProtection

    • Relationships (relationships of type 'Child' will be deleted, new relationships in the request of type 'Child' will be created. See more info about relationships: Creating parent/child relationships (

NOTE: See list of mandatory fields that always needs to be provided in the createPerson/updatePerson/replacePerson request: Managing persons (

Fields that will be kept

Field that cannot be provided through the replacePerson request will be kept.

Fields like

  • Profile picture

  • Alert settings

  • Language

  • Account setting

  • Created date - Date the user was initially created