# PutEmploymentFundByEmploymentFundId Edit a employment fund record __Activity name :__ PutEmploymentFundByEmploymentFundId __Metadata :__ Possible options for fields of the type "metadata" can be acquired (GET) by adding `/metadata` to the PUT URL. Select loket.nl (REST) API URL: /providers/employers/employees/employments/employmentfunds/{employmentFundId} Insert loket.nl (REST) API URL: /providers/employers/employees/employments/employmentfunds/{employmentFundId} Update loket.nl (REST) API URL: /providers/employers/employees/employments/employmentfunds/{employmentFundId} Delete loket.nl (REST) API URL: /providers/employers/employees/employments/employmentfunds/{employmentFundId} Select loket.nl (REST) API Operation: put /providers/employers/employees/employments/employmentfunds/{employmentFundId} - Catalog: `LoketNlRest` - Schema: `EmploymentFunds` - Field Selection Method: NotRequired - Base Path: `content` 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 | |---|:---:|:---:|:---:|---| | `body` | `string` | ☑ | | | | `employmentFundId` | `guid` | ☑ | | The unique identifier of the employment fund | | `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). | ## Columns of Table Function The columns of the table function `PutEmploymentFundByEmploymentFundId` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `deviations_employmentContributionPercentage` | `double` | | ☐ | Deviating employment contribution percentage. This value will overrule the value of the selected `fund`. Indicates percentage wise how much the employment has to contribute to the payment of the "fund" contribution. __Note:__ Records with a `startDate` before 1-1-2014 have a different regular expression__:__ ^(\d{1,3})(\.\d{1,3})?$ (a scale of 3 instead of 4). | | `deviations_totalContributionPercentage` | `double` | | ☐ | Deviating total contribution percentage. This value will overrule the value of the selected `fund`. The difference between `employmentContributionPercentage` and `totalContributionPercentage` will be paid by the employer. __Note:__ Records with a `startDate` before 1-1-2014 have a different regular expression__:__ ^(\d{1,3})(\.\d{1,3})?$ (a scale of 3 instead of 4). | | `endDate` | `datetime` | | ☐ | The end date of the entity. The date is up to and including. | | `fixedContribution_employmentContribution` | `double` | | ☐ | The employment contribution (in money) that the employee will pay instead of what the calculation of the `fund` indicates. __Note:__ Records with a `startDate` before 1-1-2014 have a different range, from 0.00 up to 9999.99 | | `fixedContribution_totalContribution` | `double` | | ☐ | The total contribution (in money) that the employer and employee pay instead of what the calculation of the `fund` indicates. __Note:__ Records with a `startDate` before 1-1-2014 have a different range, from 0 up to 9999.99 | | `fund_description` | `string(255)` | | ☐ | The description of the fund | | `fund_key` | `int32` | | ☐ | The key for the fund | | `id` | `guid` | | ☐ | The unique identifier of an object (GUID/UUID) | | `startDate` | `datetime` | | ☐ | The date on which this fund starts. A (linked chain)[./#section/Data/Date-chains] per fund is maintained within this resource. So multiple funds can be active at the same time but one specific fund can never be active multiple times at the same time. |