# DeleteAbsenceProgressByAbsenceProgressId Delete a specific Absence Progress record __Activity name :__ DeleteAbsenceProgressByAbsenceProgressId Delete an existing Absence Progress (for an employee). There always has to remain one record of absence progress for an absence. This last record is removed when the absence is deleted. Select loket.nl (REST) API URL: /providers/employers/employees/absences/absenceprogress/{absenceProgressId} Insert loket.nl (REST) API URL: /providers/employers/employees/absences/absenceprogress/{absenceProgressId} Update loket.nl (REST) API URL: /providers/employers/employees/absences/absenceprogress/{absenceProgressId} Delete loket.nl (REST) API URL: /providers/employers/employees/absences/absenceprogress/{absenceProgressId} Select loket.nl (REST) API Operation: delete /providers/employers/employees/absences/absenceprogress/{absenceProgressId} - Catalog: `LoketNlRest` - Schema: `AbsenceProgress` - 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 | |---|:---:|:---:|:---:|---| | `absenceProgressId` | `guid` | ☑ | | The unique identifier of an absence progress | | `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 `DeleteAbsenceProgressByAbsenceProgressId` 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. |