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?

• Properties method: Currently, the PropertiesContext object is not available, but we are working on reintroducing this functionality.
• Facets support: We are also working on bringing support for facets to the Query API, expected before summer.

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!

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.

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.

When building Enterspeed schemas you have almost full control over the output you return to the views. However, there are cases when working with references where you don’t have that full control. To address this, we've now introduced a first function.

When you use the children or filter function while building a reference, these functions can return multiple references and because of that the result is an array. But sometimes, you only need the first child, or your filter query includes a comparison on an ID field, and you expect just one reference. In such cases, you probably want the result as an object instead of an array with a single item. This is now possible by using the new first function.

The first function returns the first item in the result set. The item is returned as an object instead of an array with one item. If no items are found null is returned.

Read more about the first function on the Enterspeed docs site.

In the Enterspeed Management App, we've introduced an Activity log. You find it under Settings > Activity logs. The Activity log allows you to go back in time and see all activities, such as the creation, updating, and deletion of schemas, environments, source groups, and more. You can see who made the changes and when they were made. For many logs, you can even compare the new and previous values before the change.

The new Activity log is based on the new Logs UI we introduced a couple of months ago, but the default columns and filters are adjusted to fit the purpose of an activity log. Just like you know it from the logs, you can filter on different properties, set a time interval, and add or remove columns in the list. For example, you can filter by user (actor) to see all changes by a specific user within a time interval. Selecting a log message brings up the side panel, where you can see more details about the log and use shortcuts to add columns to the list or filter by specific values.

Our hope is that the Activity log can be yet another tool to help you get a better overview of what's happening on your Enterspeed tenant.

When debugging JavaScript it's often useful to use the console object to print out values to the console.

With the latest update, we've now added support for this when using the Test schema feature in the Enterspeed Management App. We hope this'll make it easier for you to debug and test your schemas.

You can read more about the console object support and see examples on the Enterspeed doc site.

By default, you get IntelliSense in the Enterspeed JavaScript schemas by the @type expression defined in the top of the schemas (/** @type {Enterspeed.FullSchema} */). However, this only provides IntelliseSense for the functions and the known properties of the source entity – not the custom properties containing all the data of a source entity.

With the introduction of the new generic versions of the Enterspeed schema types, you can now work with strongly typed custom properties in your schemas by providing a type for your source entity described in JSDoc (/** @type {Enterspeed.FullSchema} */).

If you are working with strict types of your source entities, this could be useful and make it easier for you to work with your schemas as you get IntelliSense and defined types on custom properties which could also prevent potential errors.

You can read more about the JSDoc support and see examples on the Enterspeed doc site.

The log viewer in the Enterspeed Management App just received a huge update 🪵

The update focuses on two things: Making it easier to find the right logs, and making it easier to get an overview of the logs.

With the new update, you can now filter on a long list of properties – and not only level, service, and source entity id as before. You can add multiple filters, select operators like is, is not and in – and you can even add filters directly from a specific log entry in order to find logs with similar values. This should improve your chance of finding the log entries you are logging for quite a bit. And not only a single log entry, but also other log entries leading up to the event in order to figure out what started it.

The log list has a set of default columns (Timestamp, Level, Service and Message), but from a specific log entry, you can now toggle any property to be visible in the list as well. This'll give you a better overview when you begin to dig into the list of log entries.

Besides the two new main features, there's a long list or minor improvements, like filtering on relative time intervals, improved navigation options to related objects, and more readable teaser messages.

Go ahead and check it out. We hope you enjoy the new update 🚀