Product Updates
Upcoming changes in GraphQL query complexity limit
Our GraphQL service is implementing a new change starting from June 12, 2023. GraphQL requests with a complexity score above 10,000,000 will return an error message. We have worked hard to develop a new algorithm that calculates the complexity score more precisely. It will help us prevent abuses and ensure that our GraphQL service remains fast and efficient for all customers.
The complexity score is calculated based on the number of fields requested and other factors contributing to the computational resources needed to process the query. You can read more about how we generate this score and where to obtain it on the updated doc page.
The maximum complexity score in your plan might be higher than the default. However, we encourage all customers to review their queries and optimize them to reduce their complexity score where possible. You can see what's your plan limit on your dashboard page.
As you know, our GraphQL server returns the HTTP header X-Complexity with the score of the given query. Today we have added a new header named X-Max-Complexity that shows your current plan limit. This pair of headers will help you identify which queries will start to return an error starting from June 12, and thus need a change.
If you have any questions or concerns about this change, please don't hesitate to contact our support team. We appreciate your understanding and cooperation as we make this important change.
Improved HEX notation for Color Fields in Content Delivery API
We're excited to announce that we're upgrading the management of CSS hex color notation in color fields for the Content Delivery API. Starting today, we'll be using the 8-digits hex color notation, or #RRGGBBAA, which includes the alpha channel.
Current behavior
Currently, color fields return a CSS hex string that follows the 6 digits hex color notation. Unfortunately, this notation doesn't include the alpha channel. So when you query a color field, the hex value returned may not accurately represent the color you're looking for. For example, if you query a transparent color field, you may actually get the hex string for the color white.
Here's an example of the current behavior:
{"color": {"hex": "#FFFFFF","alpha": 0,"blue": 255,"green": 255,"red": 255}}
Improved behavior
To address this issue, we're adopting the widely-used 8-digits hex color notation in the Content Delivery API. By using this notation, you'll get a more accurate representation of the color you're querying, including the alpha channel.
Here's an example of the improved behavior:
{"color": {"hex": "#FFFFFF00","alpha": 0,"blue": 255,"green": 255,"red": 255}}
Who is affected by this change?
This change will apply to all brand new DatoCMS projects created from today onwards. If you have an existing project that you'd like to update, you can manually do so in the Environment Settings:
Please note that this change cannot be undone, so we strongly recommend testing the effects in a sandbox environment before applying the change to your primary environment.
We hope this change will improve your experience when working with color fields in the Content Delivery API. As always, if you have any questions or concerns, please don't hesitate to reach out to our support team.
Introducing Fast Fork: a faster way to copy large environments
We're excited to announce our latest feature: Fast Fork. For users working with large environments, forking an environment can be a time-consuming process. Fast Fork offers a solution that can be up to 20 times faster than a regular fork. The only downside is that during the fork process, the source environment will be kept in read-only mode, which means that other users won't be able to make any changes to its content — this is similar to turning on Maintenance Mode.
Using Fast Fork on the DatoCMS interface is easy. Simply select the "Fast Fork" option when creating a fork. If a user is currently making changes to a record in the source environment, they will be warned and asked if they want to proceed anyway. This gives users the option to coordinate with other team members and avoid conflicts:
For users who prefer to use the CLI, the migrations:run and environments:fork commands support an additional flag for the fast fork option. However, unlike the interface, if a user is currently making changes to a record, the CLI will stop the operation. To proceed in any case, the user has to explicitely pass the --force option.
We hope that this new feature will help our users save time and increase efficiency when working with large environments. Check out our documentation page for all the details on Fast Fork and how to use it. Happy forking!
Deprecating the "exists" filter for string, text, and Structured Text fields
On fields of type Single-line string, Multi-paragraph text, and Structured Text, we used to allow both null value and empty strings (""), but in both cases the API would return an empty string.
The exists filter, which selects values different from null, would then return empty strings instead of null values. This behavior is confusing and unpredictable, so we decided to deprecate the exists filter for these types of field.
We created a new filter, called isPresent, that selects values that are neither null nor empty strings. It behaves as the opposite of isBlank. The exists filter will continue to work, but is now deprecated, and will be removed in future versions of our API.
Introducing Organizations for easier collaboration!
Today we are thrilled to announce the launch of Organizations: a powerful new feature that makes it easier — and more secure — to share ownership of projects with other team members!
Please read the complete announcement in our blog!
⚠️ Changing default value of string fields (canceled)
On Monday, 30th of January at 10AM (UTC+1), we are changing the default value of string fields from empty string ("") to null. We are doing this for consistency with other field types and because it was generating confusion over record filtering.
Please, check your code if this change impacts your projects in any way!
Write to our support team if you need any assistance.
We decided not to proceed with this and to find another solution.
New locales filter in tabular view, and a change in locale switch behaviour
We made some UI improvements in how locales are presented and managed in the tabular visualization of a collection, when you have a model with the option "All locales required?" disabled.
The locale switch dropdown now automatically filters out records that do not contain the selected locale — previously, it would only have the effect of showing content in the table in the selected locale, if it was available:
This change should already improve 99% of use cases, but if you need to make some more complex queries on your record list, you can use the new "Locales" advanced filter:
API cleanup for freshly created projects
We want our APIs to be as clean as possible, but we also do not want to disrupt the work of our customers. With that in mind, we have decided to apply some changes to the API only for the websites created from January 1st, 2023 onwards. Therefore, websites created in the new year will have a slightly different API:
createdAtandupdatedAtfields will be available on the content management API as part of themetaobject of theitemanditem_typeentities;the fields
createdAtandupdatedAtwon’t be available via GraphQL in the CDA: the existing_createdAtand_updatedAtwill remain as they currently are (quick take-away: in our GraphQL API, meta fields always start with an underscore 😉);legacy fields with wrong spelling like
appeareanceandcollection_appeareance, already marked as deprecated, won't be available anymore.
The changes will only impact new websites: nothing will change for existing ones or their duplicates. For any further info, please get in touch with our customer support.
New event hooks available on Plugins SDK
On plugins, it is now possible to intercept when the user wants to perform a specific action on one (or multiple) records, via a new set of event hooks:
onBeforeItemUpsert: when the user wants to save a record (both creation and update);onBeforeItemsDestroy: when the user wants to delete one (or more) records;onBeforeItemsPublish: when the user wants to publish one (or more) records;onBeforeItemsUnpublish: when the user wants to unpublish one (or more) records;
Please read our updated documentation to learn how to use them!
Single Sign-On with Google Workspaces is now available
It is now possible to automatically provision DatoCMS users using your centralized Google Workspace. Group memberships are supported too.
Read all the details on how to configure the integration. Single Sign-On is an enterprise feature: if you're interested, please contact our Sales team to activate a free 15 days trial.