rfoel
August 10, 2022, 1:52pm
1
According to the docs, updating an organization states “name” is a required field, which is not true in most cases as I want to update only a custom field sometimes.
https://developers.pipedrive.com/docs/api/v1/Organizations#updateOrganization
It was introduced in v13.2.5:
# Changelog
All notable changes to this project will be documented in this file.
The Changelog file gives an overview of all of the notable changes affecting the project.
The file format of it is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/), and the project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
For public Changelog covering all changes done to Pipedrive’s API, webhooks and app extensions platforms, see [public Changelog](https://pipedrive.readme.io/docs/changelog) with discussion area in [Developers Community](https://devcommunity.pipedrive.com/c/documentation/changelog/19).
## [Unreleased]
## 13.2.5
## Changed
- Updated `POST /notes`: parameter `content` is required
- Updated `POST /organizations`: parameter `name` is required
- Updated `POST /persons`: parameter `name` is required
- Updated `DELETE /persons`: parameter `ids` is required
- Updated `visible_to` parameter for `POST /deals` and `PUT /deals/{id}` to include type `number`
- Updated `visible_to` parameter for `POST /persons` and `PUT /persons/{id}` to include type `number`
- Updated `visible_to` parameter for `POST /organizations` and `PUT /organizations/{id}` to include type `number`
show original
In a side note, the field “name” for Person was also made required in v13.2.5 but it was updated in v14.0.1 making it not required.
# Changelog
All notable changes to this project will be documented in this file.
The Changelog file gives an overview of all of the notable changes affecting the project.
The file format of it is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/), and the project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
For public Changelog covering all changes done to Pipedrive’s API, webhooks and app extensions platforms, see [public Changelog](https://pipedrive.readme.io/docs/changelog) with discussion area in [Developers Community](https://devcommunity.pipedrive.com/c/documentation/changelog/19).
## 14.0.1
### Fixed
- Updated `PUT /persons/{id}`: parameter `name` is not required
## 14.0.0
### Changed
- Moved `v1/teams*` endpoints to `v1/legacyTeams*` as they're being deprecated because we are preparing for an upgraded version of the Teams API, which requires migrating the current functionality to a new path URL `v1/legacyTeams*`.
The functionality and [OAuth scopes](https://pipedrive.readme.io/docs/marketplace-scopes-and-permissions-explanations) of all the Teams API endpoints will remain the same.
## 13.3.4
### Changed
- Updated `PUT /productFields/{id}`: parameter `name` is not
show original
Welcome to the community, @rfoel
The name parameter indeed shouldn’t be documented as required when updating an organization. We will make sure to update our documentation!
We suggest subscribing to our Changelog to be notified about all API changes
1 Like
rfoel
August 11, 2022, 12:16pm
3
Not only in the docs but also here:
*/
updateOrganizationWithHttpInfo(id, opts) {
opts = opts || {};
let postBody = opts['basicOrganization'];
// verify the required parameter 'id' is set
if (id === undefined || id === null) {
throw new Error("Missing the required parameter 'id' when calling updateOrganization");
}
if (opts['name'] === undefined || opts['name'] === null) {
throw new Error("Missing the required parameter 'name' when calling updateOrganization");
}
let pathParams = {
'id': id,
};
let queryParams = {
};
let headerParams = {
};
1 Like
