# PatchConvertToEmployeeByConceptEmployeeId Convert a concept employee to an employee __Activity name :__ PatchConvertToEmployeeByConceptEmployeeId This endpoint "converts" the conceptEmployee to an actual employee in Loket. This means creating a number of records including Employee, Employment, WorkingHours, Wage etc. If the promotion is succesful the concept employee record will be deleted. The GUID of the conceptEmployee will be copied over to the GUID of the newly created Employee. Before performing these steps, quite a number of validations are performed to ensure that the provided information can be used to create a functionally valid employee. If the employeeNumber is empty then this will be set automatically for the employee. (i.e. highest available number +1) __Additional functionality :__ * It is possible to call an alternative functionality closely related to this functionality. This additional functionality will perform the validation ONLY, and it will NOT convert the conceptEmployee to an actual employee even when all validation rules are successful. Other than not performing the actual step of converting the employee the endpoint will behave identically to the actual endpoint. * This functionality can be applied by setting the optional X-ValidateOnly header to true Select loket.nl (REST) API URL: /providers/employers/conceptemployees/{conceptEmployeeId}/convertToEmployee Insert loket.nl (REST) API URL: /providers/employers/conceptemployees/{conceptEmployeeId}/convertToEmployee Update loket.nl (REST) API URL: /providers/employers/conceptemployees/{conceptEmployeeId}/convertToEmployee Delete loket.nl (REST) API URL: /providers/employers/conceptemployees/{conceptEmployeeId}/convertToEmployee Select loket.nl (REST) API Operation: patch /providers/employers/conceptemployees/{conceptEmployeeId}/convertToEmployee - Catalog: `LoketNlRest` - Schema: `ConceptEmployee` - Field Selection Method: NotRequired This is a read-only table function. The loket.nl (REST) API may not support changing the data or the Invantive SQL driver for loket.nl (REST) does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the loket.nl (REST) API. ## Parameters of Table Function | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `conceptEmployeeId` | `guid` | ☑ | | The unique identifier of the concept employee | | `If-Match` | `string` | ☐ | | Input the value acquired in the ETag header for concurrency control. Please note this is optional (and not recommended for most types of integrations). | | `X-ValidateOnly` | `boolean` | ☐ | | If set to true only the validations will be performed no changes will be committed. | ## Columns of Table Function The columns of the table function `PatchConvertToEmployeeByConceptEmployeeId` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `DUMMY` | `string(1)` | | ☑ | Default column added since the specification specifies that no data is returned. |