Please enable JavaScript to view this site.

Navigation: Schema: EmployerUser > Tables


Edit the details of an user__Activity name :__ PutEmployerUserByUserId__Metadata :__ Possible options for fields of the type 'metadata' can be acquired (GET) by adding `/metadata` to the PUT URL.Edit the details of an user

Catalog: LoketNlRest

Schema: EmployerUser

This is a read-only table function. The (REST) API may not support changing the data or the Invantive SQL driver for (REST) does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the (REST) API.

Select (REST) API URL: /providers/employers/users/{userId}

Insert (REST) API URL: /providers/employers/users/{userId}

Update (REST) API URL: /providers/employers/users/{userId}

Delete (REST) API URL: /providers/employers/users/{userId}

Field Selection Method: NotRequired

Base Path: content

Select (REST) API Operation: put /providers/employers/users/{userId}

Table Function Parameters

The following parameters can be used to control the behaviour of the table function PutEmployerUserByUserId. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be treated using their default values.

Value specification by position is done by listing all values from the first to the last needed value. For example with `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three.

Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third.


Data Type


Default Value





Input the value acquired in the ETag header for concurrency control. Please note this is optional (and not recommended for most types of integrations).




The unique identifier of an user


Table Function Columns

The columns of the table function PutEmployerUserByUserId are shown below. Each column has an SQL data type.


Data Type







Outcome of operation as single plain text column.


25-05-2022 14:15 Version 22.1.46-BETA+3385