See the latest new features, improvements, and product updates
We’ve identified an issue where reported storage usage was lower than actual usage over the past 1–2 weeks. This discrepancy is now being corrected, and we are in the process of correcting the storage metrics for all tenants.
No action is required from your side. We’ll remove this notice once all tenant data is fully updated.
If you have any questions, then reach out on your Slack support channel or via support@enterspeed.com.
Fetching data from Enterspeed has just become 100 times easier. With the new Query API, you can create dynamic queries on the data you have in Enterspeed. This means you can now effortlessly create product list pages, article lists, or any other type of list you need. Additionally, you can look up specific customers' orders or events within specific date ranges and locations.
The Query API introduces several new concepts, including the Index Schema, which allows you to define and manage searchable properties, and the Query API Endpoint, a new endpoint in the Enterspeed ecosystem: query.enterspeed.com.
In the Index Schema, you create and manage dynamic queries on your data.
The Query API supports filtering and sorting, and pagination. For instance, you can filter on fields defined in the Index Schema with various operators like equals and greaterThan.
For more detail, please jump to the product article 👉 The Enterspeed Query API is in preview
What’s next?
PropertiesContext object is not available, but we are working on reintroducing this functionality.How to get started
To learn more about the Query API, visit our documentation.
If you want to try out this feature, please reach out to us, and we’ll activate the feature and give you a 1:1 introduction.
We are thrilled to see how you will use the Query API to enhance your projects!
You can now get an e-mail notification whenever Enterspeed creates, updates, or resolves an incident on any of our services including:
By subscribing, you’ll receive status notifications directly if there are any changes to our system's performance and we’ll also use the updates to announce any planned maintenance windows.
Simply jump to Enterspeed status and subscribe to get the latest updates delivered straight to your inbox.
Have you ever wanted to know what a view response looks like from the Delivery API – or maybe wanted to see resolved references for a view? Good news! You can now do that directly from the Generated views panel in the Management App.
In addition to copying a CURL request from the routes list, you can now execute the request directly and view the response from the Delivery API within the app. This feature is particularly useful for seeing the full view, including resolved references, as shown in the examples below.
The statically generated view holds a single unresolved reference for a productListingView. This is how the view is stored as references are resolving during the Delivery API request.
When you execute the CURL request against the Delivery API, you can now see the full response, including the resolve productListingView reference.
We've also introduced the ability to make CURL requests by id. In the Enterspeed Delivery API, you can fetch a view in three ways: by URL, by handle, or by id. URLs and handles are routes you create using the routes function in a schema. Previously, we only provided CURL options for these explicit routes. Now, we've added the id CURL request, allowing you to fetch views without relying on explicit routes. This makes it easier to test references for these views.
If you’re (also) one of those people who enjoy insights and transparency in your services, you’re gonna like the Ingest requests tile on the dashboard that we’ve just introduced.
The new tile displays the current month’s number of ingest request. You’ll see both the total number of ingest requests and the number of changed ingest requests. These two numbers provide a change ratio, which indicates the percentage of total ingest requests that have changed.
We hope the new tile can help you understand and optimise your integrations to Enterspeed.
 |   |
Besides the ingest numbers, the new Ingest requests tile is the first tile on the dashboard where you can configure different view options for the tile. We hope to bring this concept to some of the existing tiles as well in the future.
The Versions page in the Enterspeed Management app have gotten an update. And we think you will like it 😀
Check out the features below.
Performance improvements
The page now loads faster, especially if you have many environments.
New version indication
A red dot on the version number is indicating if a newer version exists.
Deployment status
When a schema is actively being deployed, an animation will show the transition from the current version number to the new version number. As soon as the deployment is completed the version number is updated.
The new deployment indicator on the Versions page is just the first step on the way to give your more insights to the status of schema deployments.
Umbraco 15 is out – and as always, we have upgraded our integration to support the new Umbraco version 👌
Besides the support of Umbraco 15, the new package also contains some new features and fixes, like support for the new RTE editor and the option to remove trailing slashes in the URLs.
So, make sure to check out the Enterspeed package on Umbraco marketplace.
OBS, if you are using Umbraco 9 to 15, make sure to get the right package version 😉
Version 5.x is for Umbraco version is 14 or higher.
Version 4.x is for Umbraco version 9 to 13.
We’ve made a small but significant update to the Tenant Health tile. Back in warm and sunny August, we introduced the Tenant Health tile to the Overview section of the Enterspeed app home page. This tile provides a quick overview of recent errors in your transformations. However, as we received more and more questions about errors that seemingly didn’t affect anything, we realised there was room for improvement.
Upon reviewing the errors reported in the Tenant Health tile and Logs, we realised that some of the errors weren’t actually errors. When one of the millions of view generations in Enterspeed each month fails, the system automatically retries the failed job. Previously, each failed attempt was logged as an error, even if the job was retried and successfully completed moments later.
With this update, errors that are successfully retried will no longer appear in the Tenant Health tile. We apologise for any unnecessary alarm caused in the past — rest assured, move along, nothing to see here 🙆♀️
Our Algolia Destination has been updated to support partial updates. With partial updates you can add or update attributes on a record without replacing the whole record. This means that you can update a single record from multiple schemas with different properties – or you can even update a single record where only part of the data is available in Enterspeed and the rest of the attributes for the record is updated in another system.
The update also let's you decide if a partial update should create the record or not, if it doesn't already exists. This way you can have "master" of the record and only let other updates add additional attributes if the master exists.
Check out our updated Algolia Destination documentation.
Enterspeed schemas rely heavily on references and partials. When you’re working with a schema that has either references or partials, you often need to check out the content of the referenced or partial schema you’re using.
Before this update, it was honestly a bit of a hassle to find and open the referenced or partial schema. You had to open a new browser tab, navigate to the schema list, find the referenced or partial schema, and open it. But now, we’ve added a nice little shortcut.
Now, when you see references or partials, the schema alias is underlined. This means you can simply CTRL + Click the schema alias to open the schema in a new tab, right from where you are working. No more navigating away from your current schema.
Oh, and by the way, with this update we now also show warnings in the editor if you use a schema alias the doesn't exists. This makes it easier for you to spot any potential errors.
