Loket.nl REST API Data Model
DeviatingHourlyWageByDeviatingHourlyWageId |
Details of an deviating hourly wage__Activity name :__ GetDeviatingHourlyWageByDeviatingHourlyWageIdGet the details of a deviating hourly wage
Catalog: LoketNlRest
Schema: DeviatingHourlyWage
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.
Select loket.nl (REST) API URL: /providers/employers/employees/employments/deviatinghourlywages/{deviatingHourlyWageId}
Insert loket.nl (REST) API URL: /providers/employers/employees/employments/deviatinghourlywages/{deviatingHourlyWageId}
Update loket.nl (REST) API URL: /providers/employers/employees/employments/deviatinghourlywages/{deviatingHourlyWageId}
Delete loket.nl (REST) API URL: /providers/employers/employees/employments/deviatinghourlywages/{deviatingHourlyWageId}
Field Selection Method: NotRequired
Base Path: _embedded[*]
Select loket.nl (REST) API Operation: get /providers/employers/employees/employments/deviatinghourlywages/{deviatingHourlyWageId}
Table Function Parameters
The following parameters can be used to control the behaviour of the table function DeviatingHourlyWageByDeviatingHourlyWageId. 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.
Name |
Data Type |
Required |
Default Value |
Documentation |
|---|---|---|---|---|
deviatingHourlyWageId |
guid |
☑ |
|
The unique identifier of the record |
Table Function Columns
The columns of the table function DeviatingHourlyWageByDeviatingHourlyWageId are shown below. Each column has an SQL data type.
Name |
Data Type |
Label |
Required |
Documentation |
|---|---|---|---|---|
endDate |
datetime |
|
☐ |
The end date of the entity. The date is up to and including. |
id |
guid |
|
☐ |
The unique identifier of an object (GUID/UUID) |
payrollComponent_description |
string(14) |
|
☐ |
The description of the payroll component |
payrollComponent_key |
int32 |
|
☐ |
The number for the payroll component. |
startDate |
datetime |
|
☐ |
The date on which this DeviatingHouryWage starts.A (broken chain)[./#section/Data/Date-chains] per DeviatingHouryWage is maintained within this resource. So multiple DeviatingHouryWages can be active at the same time but one specific DeviatingHouryWage can never be active multiple times at the same time. |
value |
decimal |
|
☐ |
The value for the selected payroll component. |
13-05-2022 15:37 Version 22.1.40-BETA+3374
