You can now read Delivery views as your own C# types. Keep the flexible fetch you know, but de-serialise per-view into real models with IntelliSense and compile-time safety. No more rummaging through dictionaries.

What’s new

• Typed variant of Fetch: fetch as usual, then read each view with GetContent().
• Per-view typing: mix multiple handles (e.g. article, navigation, footer) in one request and deserialise each into its own model.

Why it matters

• Fewer runtime surprises: let the compiler and your IDE do the heavy lifting.
• Cleaner contracts: define a C# model instead of magic dictionary keys all over your code base.
• Less boilerplate: no need for custom serialization.

Example: multiple views, multiple types

Fetch several views in one go, then read each as its own model:

Useful links

• Delivery SDK (.NET) repo & README – install, register, usage, and strongly-typed examples. GitHub
• Docs: Delivering data – overview of Delivery API. Enterspeed Documentation | Enterspeed Docs

Thanks to the community

This shipped because a user opened a clear feature request with suggested behaviour. So, keep the issues and PRs coming – we’re listening.

We’ve improved how you track deployments in the Activity section. Instead of just seeing that “someone deployed something,” you now get full transparency:

• Clear logs showing deployments – including who did it
• Optional comments attached to each deployment, so you can understand the why
• See which items were deployed together
• Detailed history for individual schemas, including when they were created or published

These improvements make it easier to keep track of projects and give you a complete overview of who did what, when, and why.

Go to your activity log to see what you can do: https://app.enterspeed.com/settings/activity-logs

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.

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.

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.

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 🚀

Enterspeed is no different from other software; things go wrong, and then you need to figure out why. So we are very happy to announce that you can now access the logs for our destinations the Enterspeed Management app.

If you just want to see how it works, then head over to Settings and the Logs section ➡️

If you want to read more about the feature, then we recommend reading our What to Do When Things Go Wrong blog post?

A couple of months ago, our Delivery REST API introduced a POST request version, allowing you to request up to 1,000 views in a single request. With the introduction of the FetchMany method, this is now also possible through our .NET SDK.

Just as in the REST API, it’s possible to fetch views by handles and IDs, as shown in the example below:

Simply install or update the package to version 1.4.0 from NuGet.

In addition to the new method, the new package version also includes dependency updates to System.Text.Json to support version 8.

As you probably know, you can organize your schema in folders in the Enterspeed app, making it easier for you to find the schema you're looking for.

Now we also brought the folder support into the CLI. This means that you'll see and work with the same folder structure on your local disk as you do in the Enterspeed App. You can move schemas from one folder to another locally and update them in the Enterspeed app.

As a result, the old static partials folder is now gone and the type is reflected in the file name instead (schemaAlias.schemaType.js), which also opens up for supporting new types of schemas in the future.

If you already have your schemas locally and you want to upgrade the CLI, simply clear your local schemas folder and run the schemas clone command to get the new schema name and folder structure.