DatoCMS changelog for new features and general improvements

Images API

## [AVIF support + IPTC Passthrough](https://www.datocms.com/product-updates/avif-support-iptc-passthrough.md)

[date: 2022-01-27T11:20:32.554+01:00]

AVIF is now the default format across all accounts if you use `auto=format`. AVIF format can also be forced as the output format with `fm=avif`. File sizes should drop by nearly 60% compared to JPEG & 35% compared to WebP, so that's awesome news for every project.

We've also made available the [`iptc=allow`](https://docs.imgix.com/apis/rendering/format/iptc) parameter to allow IPTC metadata (which contain attribution info) to pass through from the original JPG image to the transformed image.

UI Improvement

## [Automatically create modular blocks if only one type required](https://www.datocms.com/product-updates/automatically-create-modular-blocks-if-only-one-type-required.md)

[date: 2021-12-23T16:50:15.604+01:00]

In a modular content field, if you specify only one type of required block and you add a validation requiring a minimum number of blocks, like here for example:

(Image content)

We go ahead and by default create the required empty blocks for you when you create a new record, like this:

(Image content)

So your editors will see from the get go all the fields that they will need to populate and save a few clicks!

UI Improvement

## [New notice type for build triggers](https://www.datocms.com/product-updates/new-notice-type-for-build-triggers.md)

[date: 2021-12-06T17:20:54.443+01:00]

We have just added a new type of notice for build triggers:

(Image content)

So that now you can see at a glance if it's a build trigger notice and you don't risk missing it thinking it's a record saving or something else.

Content Management API

## [Creation of new records via API no longer requires to specify all fields](https://www.datocms.com/product-updates/creation-of-new-records-via-api-no-longer-requires-to-specify-all-fields.md)

[date: 2021-11-26T10:35:17.150+01:00]

This change was long overdue, and we're glad we were able to address it! 🥳

Suppose you have ie. a model with 10 fields, 9 of which are optional. Until now, when creating a record, you were required to specify... all 10 fields. If you didn't want any value for the optional ones, you were required to pass a `null` value in any case, or the API call would fail:

```javascript
const { SiteClient } = require("datocms-client");const client = new SiteClient("YOUR-API-TOKEN");const record = await client.items.create({  itemType: "1234",  requiredField: "Lorem ipsum",  optionalField1: null,  optionalField2: null,  optionalField3: null,  optionalField4: null,  optionalField5: null,  optionalField6: null,  optionalField7: null,  optionalField8: null,  optionalField9: null,});
```

In addition to being redundant and inconvenient, this was a maintainability problem over time, because when a new optional field gets added on the model, you need adapt every script and add that `null` value. Well, now optional fields can be omitted from the payload during creation:

```javascript
const record = await client.items.create({  itemType: "1234",  requiredField: "Lorem ipsum",});
```

Nice, simple and clean. Happy friday!

Content Management API New

## [Splitted create/duplicate records permission](https://www.datocms.com/product-updates/splitted-create-duplicate-record-permission.md)

[date: 2021-11-15T10:13:23.658+01:00]

With today's update, we decided to split two permissions in order to give you a more fine grained permission system.

### Before

(Image content)

Create/Duplicate permission, as it was before

### After

(Image content)

New splitted permission: Create and Duplicate record permissions

### What happened to existing roles in my project?

This change did not alter what your users were already able to do, or not to do. For instance, if an existing role had the ability to "Create/duplicate" records, the same role has both the permissions ("Create" and "Duplicate") defined.

Content Delivery API

## [Get locales list from GraphQL](https://www.datocms.com/product-updates/get-locales-list-from-graphql.md)

[date: 2021-10-29T13:38:27.391+02:00]

You can now query the list of existing locales directly from GraphQL:

```graphql
query Locales {  _site {    locales  }}
```

And you get back the array of the locales:

```json
{  "data": {    "_site": {      "locales": [        "en",        "it",        "ar"      ]    }  }}
```

UI Improvement

## [Better support for RTL languages](https://www.datocms.com/product-updates/better-support-for-rtl-languages.md)

[date: 2021-10-26T11:37:28.220+02:00]

We have improved our support to RTL languages by automatically switching text fields to RTL when necessary.

This choice is made automatically depending on the language selected.

New

## [Added length validation to Structured Text fields](https://www.datocms.com/product-updates/added-length-validation-to-structured-text-fields.md)

[date: 2021-10-12T15:32:13.252+02:00]

We have just added the possibility of specifying a length validation on Structured Text fields, as was already possible for string and text fields:

(Image content)

New

## [Ending support for Internet Explorer 11](https://www.datocms.com/product-updates/ending-support-for-internet-explorer-11.md)

[date: 2021-10-08T15:30:30.642+02:00]

In more than one official communication, Microsoft has announced the end of life for Internet Explorer 11:

-   On August, it [removed support for IE11 for all Microsoft 356 online services](https://techcommunity.microsoft.com/t5/microsoft-365-blog/microsoft-365-apps-say-farewell-to-internet-explorer-11-and/ba-p/1591666);
-   In May, it announced the [permanent retire of IE11](https://blogs.windows.com/windowsexperience/2021/05/19/the-future-of-internet-explorer-on-windows-10-is-in-microsoft-edge/) as of June 2022.
    

Beginning October 25, 2021, **DatoCMS will no longer support Internet Explorer 11 (IE11)** and users may have a degraded experience, or be unable to connect to our apps and services.

If you're still using Internet Explorer, you will need to transition to Microsoft Edge (or any other modern browser) before October 25 to start enjoying a faster, more secure and more modern browsing experience.

This change will allow us to work faster, and offer better performance on the latest browsers.

UI Improvement

## [Copy structured text from main locale](https://www.datocms.com/product-updates/copy-structured-text-from-main-locale.md)

[date: 2021-09-27T10:00:00.227+02:00]

You can now copy the content of a localized structured text from the main locale to the others, with just one click:

(Video content)