Roles and modulesRemoveRoleFromEmployeeByGuid

RemoveRoleFromEmployeeByGuid

Organisation service 1.9: Remove a role from an employee

ServiceOrganisation 1.9
EndpointPOST https://app{server-number}.timelog.com/{account}/WebServices/Organisation/V1_9/OrganisationServiceSecure.svc
SOAPActionhttp://www.timelog.com/api/tlp/v1_9/OrganisationService/RemoveRoleFromEmployeeByGuid
Content-Typetext/xml; charset=utf-8
AuthenticationA token from GetToken
Changes dataYes
Safe to retryYes

How it works

No last-administrator guard. Removing an employee's personal role is not prevented. Role GUIDs come from GetRoles / GetEmployeeRoles.

Parameters

Each parameter has one label: Required, Conditional (required depending on other values) or Optional. Send them in the order shown.

employeeGuidguid
Required

GUID of the employee.

roleGuidguid
Required

Role.ID from GetRoles / GetEmployeeRoles.

tokenSecurityToken
Required

The token from GetToken: Initials, Expires and Hash, sent back unchanged.

Request

POST /{account}/WebServices/Organisation/V1_9/OrganisationServiceSecure.svc HTTP/1.1
Host: app{server-number}.timelog.com
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://www.timelog.com/api/tlp/v1_9/OrganisationService/RemoveRoleFromEmployeeByGuid"

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
                  xmlns:org="http://www.timelog.com/api/tlp/v1_9"
                  xmlns:tok="http://www.timelog.com/api/tlp/v1_3">
  <soapenv:Body>
    <org:RemoveRoleFromEmployeeByGuid>
      <org:employeeGuid>{employeeGuid}</org:employeeGuid>
      <org:roleGuid>{roleGuid}</org:roleGuid>
      <org:token>
        <tok:Initials>{Initials from GetToken}</tok:Initials>
        <tok:Expires>{Expires from GetToken, unchanged}</tok:Expires>
        <tok:Hash>{Hash from GetToken}</tok:Hash>
      </org:token>
    </org:RemoveRoleFromEmployeeByGuid>
  </soapenv:Body>
</soapenv:Envelope>
Replace every {…} placeholder with your own value.

Response

The call returns the standard response envelope. Check ResponseState first: a failed call still returns HTTP 200.

ResponseStatestring
Required

Success, Invalid or Error.

ErrorCodeinteger

0 on success, otherwise the error code. See Errors.

ReturnEmployeeHeader[]

Response<EmployeeHeader> after the save. Never - failure is an Error envelope with an empty Return.

Example response

HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
  <s:Body>
    <RemoveRoleFromEmployeeByGuidResponse xmlns="http://www.timelog.com/api/tlp/v1_9">
      <RemoveRoleFromEmployeeByGuidResult xmlns:a="http://api.timelog.com"
                                          xmlns:b="http://www.timelog.com/api/tlp/v1_9"
                                          xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
        <a:Return>
          <b:EmployeeHeader>
            <b:ID>3f2504e0-4f89-41d3-9a0c-305000000001</b:ID>
            <b:EmployeeID>1001</b:EmployeeID>
            <b:UserName>Example user</b:UserName>
            <b:Initials>ABC</b:Initials>
            <b:FirstName>Example first</b:FirstName>
            <b:LastName>Example last</b:LastName>
            <b:EmployeeNo>1001</b:EmployeeNo>
            <b:Fullname>Example</b:Fullname>
          </b:EmployeeHeader>
        </a:Return>
        <a:ReturnTypeDescription>EmployeeHeader</a:ReturnTypeDescription>
        <a:Request>…</a:Request>
        <a:ResponseState>Success</a:ResponseState>
        <a:Messages>
          <a:APIMessage>
            <a:Message>Duration of call was 0,0421337 sec.</a:Message>
            <a:Severity>Message</a:Severity>
            <a:ErrorCode>0</a:ErrorCode>
          </a:APIMessage>
        </a:Messages>
        <a:ErrorCode>0</a:ErrorCode>
        <a:IsReturnPaged>false</a:IsReturnPaged>
        <a:TotalPageCount>0</a:TotalPageCount>
      </RemoveRoleFromEmployeeByGuidResult>
    </RemoveRoleFromEmployeeByGuidResponse>
  </s:Body>
</s:Envelope>
Illustrative example: built from the service description (WSDL) in the same format as a real response, with made-up values. The Request block is shortened.

Errors

All errors come back with HTTP 200: check ResponseState, ErrorCode and Messages. The errors every operation can return (expired or invalid token, API not enabled, HTTPS required, general errors) are listed once in Responses and errors.

Errors specific to this operation:

ResponseStateErrorCodeMessageWhat it meansWhat to do
Error40001Error during call on TimeLog.API, Message 'The role could not be found'No role with this GUID.Take Role.Name / Role.ID from GetRoles.
Error40001Error during call on TimeLog.API, Message 'Object reference not set to an instance of an object.'employeeGuid unknown.Take the GUID from EmployeeHeader.ID. Do not retry.
Error40001Error during call on TimeLog.API, Message 'The user violates the Business Rules for users'Save refused - typically no employee-edit privilege for this employee.Check the integration user's employee privileges first; then uniqueness of initials / user name; then the referenced data.