Create timeRegistrationEntry
Creates a timeRegistrationEntry in Business Central.
HTTP request
Replace the URL prefix for Business Central depending on environment following the guideline.
POST businesscentralPrefix/companies({companyId})/timeRegistrationEntries({timeregistrationId})
POST businesscentralPrefix/companies({companyId})/employees({employeeId})/timeRegistrationEntries({timeregistrationId})
Request headers
Header | Value |
---|---|
Authorization | Bearer {token}. Required. |
Content-Type | application/json |
If-Match | Required. When this request header is included and the eTag provided does not match the current tag on the timeRegistrationEntry, the timeRegistrationEntry will not be updated. |
Request body
In the request body, supply a JSON representation of a timeRegistrationEntries object.
Response
If successful, this method returns 201 Created
response code and a timeRegistrationEntries object in the response body.
Example
Request
Here is an example of a request.
POST https://{businesscentralPrefix}/api/v2.0/companies({id})/timeRegistrationEntries
Content-type: application/json
{
"employeeId": "258bb9c0-44e3-ea11-bb43-000d3a2feca1",
"employeeNumber": "AH",
"jobId": "00000000-0000-0000-0000-000000000000",
"jobNumber": "",
"jobTaskNumber": "",
"date": "2019-02-02",
"quantity": 5
}
EmployeeId can be used instead of employeeNumber.
Response
HTTP/1.1 201 Created
Content-type: application/json
{
"id": "1a8b1fec-c0e3-ea11-aa60-000d3ad7cacb",
"employeeId": "258bb9c0-44e3-ea11-bb43-000d3a2feca1",
"employeeNumber": "AH",
"jobId": "00000000-0000-0000-0000-000000000000",
"jobNumber": "",
"jobTaskNumber": "",
"absence": "",
"lineNumber": 10000,
"date": "2019-02-02",
"quantity": 5,
"status": "Open",
"unitOfMeasureId": "56a6738a-44e3-ea11-bb43-000d3a2feca1",
"unitOfMeasureCode": "HOUR",
"lastModfiedDateTime": "2020-08-21T15:13:58.87Z"
}
See also
Tips for working with the APIs
Error Codes
timeRegistrationEntries
Get timeRegistrationEntries
Patch timeRegistrationEntries
Delete timeRegistrationEntries
Commentaires
https://aka.ms/ContentUserFeedback.
Bientôt disponible : Tout au long de 2024, nous allons supprimer progressivement GitHub Issues comme mécanisme de commentaires pour le contenu et le remplacer par un nouveau système de commentaires. Pour plus d’informations, consultezEnvoyer et afficher des commentaires pour