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.

Umbraco has launched Umbraco 14 – and we have launched our integration for it 👌

The Umbraco 14 upgrade is a pretty significant step forward in their back office, which is now based on modern frontend technologies – but in the tried and tested Umbraco back office we all know (and love).

The Enterspeed Umbraco package is now updated and supports all versions from Umbraco 7 to Umbraco 14.

So, no matter if you’re looking to migrate a legacy Umbraco site or wish to utilise Enterspeed in a new and modern Umbraco 14 stack, we can support it 😊

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.

You can now sign in to Enterspeed using your Microsoft Entra ID account! If you have a work account with Microsoft Entra ID, we encourage you to start using it for the Enterspeed app.

Setting it up is a simple two-step process:

• Click the Entra ID sign-in button
• Contact us via your Slack support channel or email us at support@enterspeed.com.

While we’re working our magic to associate your Entra ID sign-in with your tenants, you can still use your regular login and password—no need to panic ☺️

For more details, check out our Docs.

Sometimes, you end up creating duplicates, when you create URLs and handles from a large CMS installation and various other sources in the Enterspeed Management app. In the app, URLs and handles are collectively referred to as routes, and these routes are created during processing. Enterspeed allows developers a lot of flexibility in creating routes, but since Enterspeed relies on the source systems, it'll generate duplicate routes if that’s how the data is structured.

It requires careful developers consideration, when you create the correct route since everything happens asynchronously, without direct human oversight, and across multiple data sources. Over the past few months, we've tweaked almost every part of our route processing to provide developers with clear insights into the routes that are created.

Below is an example from the Route inspector that shows the duplicates, the schema, and the source entity from which the route originates.

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<MySourceEntityType>} */).

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.