Product Updates

DatoCMS changelog for new features and general improvements
February 25th, 2019
Slugs now auto-generated on existing records
Content Management APIUI ImprovementNew

A small but handy change just landed: when you add a slug field to a model, if the model already contained some records, they will get a proper slug generated!

February 25th, 2019
Added `firstPublishedAt` to both CMA and CDA
Content Delivery APIContent Management API

We just introduced a new meta field to records which represents the first time a record gets published: perfect to use in blogs as the publication date of an article, for example.

You can fetch, filter and order records using _firstPublishedAt on our GraphQL Content Delivery API:

{
allBlogPosts(orderBy: [_firstPublishedAt_DESC]) {
title
slug
author { name }
_firstPublishedAt
}
}

The meta field is also present in our CMA, and in the administrative interface:

January 29th, 2019
Ability to restrict access to GraphQL/REST endpoints
Content Delivery APIContent Management API

We just made possible to specify which API endpoints an API token can access:

This will prevent from using your ie. production API token to read temporary/draft content using the GraphQL preview endpoint.

January 24th, 2019
Change in Content Delivery API GraphQL schema
Content Delivery API

On February 4, at 11:00 CEST we'll publish a small change to the GraphQL types of our Content Delivery API.

If you want to get the value of a field for every locale of the project, you can use the following query:

query {
allBlogPosts {
_allTitleLocales {
locale
value
}
}
}

Right now the type for the _allTitleLocales field is [PageModelSlugMultiLocaleField]. After the change, the name of the type will simply be [SlugMultiLocaleField]. That is, the prefix {MODEL_NAME}Model will be dropped.

This change will drastically reduce the overall number of GraphQL types on multi-language project, reducing both our response times (by up to ~25%) and time to process the schema on your side.

The large majority of our users won't need to do anything, but if your codebase do relies on GraphQL type names, please make sure to do the necessary adjustments before February 4 or contact us if you need more help/information.

January 21st, 2019
View Netlify logs under Settings > Activity Log
UI Improvement

We've just made possible to see the log of a Netlify build related to a DatoCMS publication from under the Activity Log section of your administrative area:

Quite handy to quickly investigate why some build failed without having to leave the DatoCMS interface!

December 16th, 2018
Improved management of API rate limits
API Clients

We've just pushed a new version of our JS and Ruby clients that will automatically retry requests after the correct amount of time if they encounter a 429 Too Many Requests response from our Content Management API when exceedings rate limits.

Upgrade your projects to the latest version of our clients to take advantage of this!!

December 3rd, 2018
Scheduled publishing
New

A long awaited feature is finally online! You can now set a future publication date for your items!

November 29th, 2018
Role-based permissions
New

Your organization’s workflow gets another boost thanks to the ability to let users only manage records created by users with the same role!

November 23rd, 2018
Configurable Twitter card
New

Up until now, all Twitter cards generated by DatoCMS had the twitter:card property set to summary. Now you can change this settings in every SEO field!

You can also configure the stardard Twitter card in the project global settings:

Upgrade to the latest DatoCMS clients to start using this feature on your frontend website!

November 23rd, 2018
Save frequent searches as filters
New

Filters can now be saved and shared between users for easy reuse.

Everyone can freely save personal filters, but only users whose roles allow the creation of shared filters can make them available for everyone: