API changelog

Fixed

• Input the API cannot store (NaN, Infinity, NUL characters, unpaired surrogates, over-long indexed text, deep nesting) returns code 117 instead of a server error.RESTGraphQL
• convert… mutations apply their validationLevel.GraphQL
• restoreLead, restoreOpportunity and restoreQuote return the record when it was not deleted, instead of null.GraphQL
• reactivateLeadOppty and bulkReactivateOpportunity keep the closing date when none is sent, and bulkReactivateQuote keeps the expiration date.GraphQL
• The OpenAPI document no longer lists validation-level on DELETE, batch-delete and batch-restore, which never accepted it.REST
• PATCH /entities/FieldMappings/{id}, batch-delete of folders and project objectives, and batch-modify of targets work instead of failing with a server error.REST
• batch-modify finds IDs written in upper case, and answers code 143 for a record the caller cannot see instead of a server error.REST
• A query string that is not UTF-8 and a malformed AppointmentSchedules body answer HTTP 400 instead of a server error.REST
• WebResources with an unknown entity answer code 117, and a Phones update with an unknown ID code 143, instead of a server error.REST
• TextMessages and TextMessageConversations answer DELETE and batch-delete with code 171 and batch-modify with 116, instead of a server error.REST
• EntityFitnessIndicators without settings answer ERROR_PARAMETER_MISSING, and ProfileRelations and ClientFavorites need exactly one target, instead of a server error.REST

Fixed

• 6.5.2Unknown paging cursors and sorts through a relation to the same entity (parent_account.name) return code 117, and a picture without url code 119, instead of a server error.RESTGraphQL
• 6.5.2Merging a record into itself is refused with code 117; it used to delete the only copy of the record.RESTGraphQL
• 6.5.0Malformed settings, tag, filter, orderBy, duration and meeting_url input returns code 117 instead of a server error.RESTGraphQL
• 6.5.0PATCH with validation-level on draft-and-publish entities (Fields, the record types, Translations …) no longer fails with a server error.REST
• 6.5.0A task or appointment with project_relations: null is saved with no project relations.RESTGraphQL
• 6.5.0An appointment created by an integration with a Microsoft Teams or Zoom meeting_url and no join URL gets its meeting created for its owner.RESTGraphQL

Fixed

• 6.4.7A wrong rollup definition on a new field returns ERROR_INVALID_ROLLUP_CONFIGURATION (code 2019) instead of a server error.RESTGraphQL
• 6.4.6With validation-level bit 16, a relation to a record that does not exist returns ERROR_RELATIONS_DOESNT_EXIST (code 120) instead of a server error.RESTGraphQL
• 6.4.6Step checklist items can be created without sort_order, and are added at the end of their step; it used to fail with a server error.RESTGraphQL
• 6.4.2Responses are compressed with br, gzip or deflate as Accept-Encoding allows; 6.4.0 and 6.4.1 could answer with zstd, sometimes without a Content-Encoding header.RESTGraphQL
• 6.4.0getPublished on draft-and-publish repositories, such as field, accepts limit and offset; it used to fail with them.GraphQL

Fixed

• 6.3.7Creating a field of a rollup type without a rollup object is refused with code 117 instead of a server error.RESTGraphQL
• 6.3.7Creating a field that has no source type works instead of failing with a server error.RESTGraphQL
• 6.3.7quote.autoPrefill prefills from the first quote process that has a quote type, or from the process of the type in targetEntityTypeId, instead of failing when the space's first quote process has none.GraphQL
• 6.3.5advancedFormula on a field draft (field.getDrafts, field.getDraftById) returns the draft's own formula, or null, instead of the published one.GraphQL
• 6.3.3GET /entities/CustomEntityRelationDatas and other lists that read custom-entity relations no longer fail now and then with HTTP 500; in the rare case that caused it, revision is null.REST
• 6.3.2Completing a recurring task, or moving its due date with applyRecurrence, creates the next task even when it would fail the space's form rules, instead of refusing the update with code 40000.RESTGraphQL
• 6.3.2A list that filters on a relation and sorts by the same relation, such as filter[product.name] with order-by=product.name, returns its records instead of a server error.RESTGraphQL
• 6.3.2Reading e-mails no longer fails now and then with a server error for users of company or shared mailboxes.RESTGraphQL
• 6.3.0An API application whose e-mail permission is Read gets the subject, body, bodySummary, sentiment and documents of e-mails, which were empty unless it had Write.RESTGraphQL
• 6.3.0A product line (OpptyProductRelations) without oppty_id, quote_id or online_form_id is refused with code 119 instead of a server error.RESTGraphQL
• 6.3.0Updating a relation record onto a pair that exists as a deleted row is refused with code 2002 instead of a server error.RESTGraphQL
• 6.3.0batch-delete of several product lines and POST /entities/ApprovalProcesses no longer fail with a server error.REST

Fixed

• 6.2.3A field whose advanced formula is nested too deeply, such as a long chain of IFs, is refused with code 117 instead of failing with code 1000.RESTGraphQL
• 6.2.0A contains filter on a multi-select checkbox field matches the records that have the option checked instead of always failing, and a value that is not an option ID is refused with code 117.RESTGraphQL
• 6.2.0Creating a lookup field without its lookup definition, or with an incomplete or unknown one, is refused with code 119 or 117 instead of a server error.RESTGraphQL
• 6.2.0PATCH /entities/Targets/{id} and PATCH /entities/Phones/{id} work and keep the fields that are not sent, instead of failing with code 1000.REST
• 6.2.0POST with a validation-level on the record type entities, Webresources, FieldPermissions and CustomEntityTypes is accepted, with no effect, instead of failing with a server error.REST
• 6.2.0A profile relation may point at a deleted profile instead of being refused with code 120.RESTGraphQL
• 6.2.0An appointment's meetingUrl without a join URL is null instead of a GraphQL error, and a failed meeting creation no longer stores a partial meeting_url.RESTGraphQL

Fixed

• 6.1.4PATCH /entities/Fields/{id} with name_translations: null is refused with code 117 instead of a server error.REST
• 6.1.4Tasks created by a recurrence get the owner of the task they repeat instead of no owner.RESTGraphQL
• 6.1.4createImageCloudObject called with API application credentials creates the image, with creatorId null, instead of failing with code 1000.GraphQL
• 6.1.3An appointment invitee with invitee_type 1 (Scheduled) and no contact_id is stored as sent, keeping its first_name and last_name, instead of being replaced by a matching contact.RESTGraphQL
• 6.1.1The custom_entity relation of rows that point at custom-entity records is filled for every row when one request reads records of several custom entities.RESTGraphQL
• 6.1.1An opportunity update that adds a revenue_schedule back to a won opportunity after its closing date changed succeeds instead of failing with code 1000.RESTGraphQL
• 6.1.1A file created or updated with a url on Coevera's own file storage host is treated as a stored file instead of being downloaded again.RESTGraphQL
• 6.1.0An opportunity or quote update that sets a required field to null together with product_relations gets a validation error and changes nothing, instead of a server error or a partial write.RESTGraphQL
• 6.1.0Restoring a deleted revenue schedule on a won or lost opportunity is accepted instead of refused with code 2002.RESTGraphQL
• 6.1.0ForecastEntity.targetGoal returns 0 for a target period with an open end instead of an error.GraphQL
• 6.1.0bulkUpdateAppointment with linkAttendees: true matches attendee e-mails to users, contacts and accounts ignoring case.GraphQL