Our September 26^th 2023 release, v2023.19, introduces: pagination for Imports in your Dashboard; expired Downloads no longer being visible in your Dashboard; Custom Attribute Description editing; and new SMS Blocked Event mapping.

For additional information on these updates please read the Dashboard, Data Source Mappings, and Events sections of this article.

For bug fixes, please read the Bug Fixes section of this article.

Dashboard

Learn more - Dashboard

If you are viewing your Imports and there is a large volume, you will find the load time increases with the number of files you Import. To decrease this load time we have introduced Import pagination, as we have done with many other areas of our Platform. As a refresher, pagination is the approach to taking a list of items and splitting it up into smaller lists. In our case, those list sizes are 25 by default. This means that our servers only need to provide your computer with 25 items, and your computer only needs to load 25 items. This can have a significant impact when compared to loading potentially hundreds of items.

File names have been blurred for security but can see the available pagination and values in the image below:

Within the Downloads section of your Dashboard, you will also find that a change has been made which will reduce load times. Expired Downloads will no longer be displayed. This will reduce both load times and clutter.

As an example, here is a 2-month expired Download that will no longer be displayed:

Data Source Mappings

Learn more - Data Source Mappings

In the previous release, we introduced descriptions for your Custom Attributes. When they were introduced, you could add the description when you created the attribute, but you could not edit them after. You now have the capability to edit them after they are created.

Click on a Draft Data Source Mapping, and then the name of your Custom Attribute. You will then be met with this screen for editing:

Events

Learn more - Events

Capturing data and surfacing it for investigation is critical for diagnosing any issues with your deliverability. In order to surface that information more conveniently, all error codes returned by Twilio that were not previously mapped to an SMS Event will now be mapped to the SMS Blocked Event. This means that if you are capturing this information in your Exports or Insights, then you will see the Twilio errors in the SMS Blocked Event. It also means this information will be surfaced in your Customer Trail.

Although these cases are unlikely, you can be assured that they will be readily available for diagnosis if they do occur.

Bug Fixes