title | description | services | documentationcenter | author | ms.localizationpriority | ms.subservice | doc_type |
---|---|---|---|---|---|---|---|
Update paymentMethods |
Updates a payment method object in Dynamics 365 Business Central. |
project-madeira |
SusanneWindfeldPedersen |
medium |
d365-business-central |
apiPageType |
Namespace: microsoft.graph
[!INCLUDE beta-disclaimer]
Update the properties of a payment method object for Dynamics 365 Business Central.
[!INCLUDE national-cloud-support]
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.
[!INCLUDE permissions-table]
PATCH /financials/companies/{id}/paymentMethods/{id}
This method supports the OData Query Parameters to help customize the response.
Header | Value |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Content-Type | application/json |
If-Match | Required. When this request header is included and the eTag provided doesn't match the current tag on the paymentMethods, the paymentMethods won't be updated. |
In the request body, supply the values for relevant fields that should be updated. Existing properties that aren't included in the request body maintains their previous values or be recalculated based on changes to other property values. For best performance, you shouldn't include existing values that haven't changed.
If successful, this method returns a 200 OK
response code and an updated paymentMethods object in the response body.
Request
The following example shows a request.
PATCH https://graph.microsoft.com/beta/financials/companies/{id}/paymentMethods/{id}
Content-type: application/json
{
"displayName": "Personal Check Payment",
}
Response
The following example shows the response.
Note: The response object shown here might be shortened for readability.
HTTP/1.1 200 OK
Content-type: application/json
{
"id": "id-value",
"code": "CHECK",
"displayName": "Personal Check Payment",
"lastModifiedDateTime": "2017-03-22T08:35:48.33Z"
}