#EPU 6: Organising schemas like a boss 😎
In this Enterspeed Product Update, we got a lot of schema-related goodies for you. Not only is it now easier to quickly create a schema – but we have also introduced a new way to keep them organised.
And as always, we got a lot more up our sleeve – so let’s dive in.
When building large sites, you often need to create a lot of specific schemas. As the number of schemas grows, so does the complexity.
You guys started asking for a better way to organise and keep track of your schemas. And just like a mad scientist we grabbed our lab coat (hoodie) and headed straight to the lab (VS code).
The result is schema folders. Instead of having all your schemas in one long table, you can now organise them into folders.
Simply add a slash (/) in your schema name and the text before will be transformed into a folder – pretty neat!
To keep it easy and manageable, we've limited the number of folder levels to two. This means you can organise your schemas into folders and subfolders.
For instance, a schema with the name “Global/Various/Link” will be transformed into a schema with the name “Link”, located in the subfolder “Various”, which is located in the folder “Global”.
Neat! To quote old Benjamin Franklin: “A place for everything, everything in its place”.
feature Prefill your schemas upon creation
Now it’s quicker and easier to create a schema. When creating a new schema, you now have the option to select a source.
Selecting a source will automatically prefill your schema with the available source entity types. We've also created a “dynamic mapping”-property, which lists all the data available for the source entity. That way it’s easier to quickly test your sources.
feature Create references across data sources
When creating a reference, you are now able to define a different source. You do this by adding the “source”-property and making it equal to the desired source group alias.
By that, you now can use a view that isn't in the same source group as the rest of the schema.
Please note, that the “source”-property only can be used if “originId” is used. If “id” is used the source of the id will take priority over the source.
feature V2 Delivery API
We released a new version of our Delivery API – version 2. The new version now supports multiple handles for the same schema.
In version 1 the schema alias is used as the key for a handle. Because of that, it’s not possible to fetch multiple handles of views generated by the same schema.
In version 2, however, the key is changed to the handle name, meaning that you can fetch multiple handles even though they are generated by the same schema.
We’ve also simplified the API and made it "cleaner". First, the key is the same as the handle name you request and not a schema alias you may or may not know about.
Second, we have removed the id, type, and view property and made the view data inline for view references – making it much cleaner for the client.
Last but not least, we’ve added the "missingViewReferences" in the meta field, which makes it easy for you to debug missing view references. All missing view references get listed here with the id of the missing view and a path of where the view is missing.
Improvement Source group is now displayed in source dropdown
When selecting a source on the Source entities page, Generated views page, etc. you can now see which source group each source belongs to.
Thus, you can easily distinguish between similarly named sources.
Improvement Duplicate partial schema
Need to duplicate a partial schema? No problem.
You can now easily duplicate your partial schema, just like you can your regular schema. Select “duplicate” in the settings menu, which you’ll find in the partial schemas overview.
Improvement Avoid accidentally deleting environments
Friends don’t let friends accidentally delete an environment in use!
And at Enterspeed, we’re most definitely your friend, so we’ve made sure this won't happen on our watch.
As a security, environments that are referenced from a data source or environment client can no longer be deleted.
If you need to delete an environment, you will first need to unlink it from your data source and/or environment client.
Improvement Dedicated resources for Enterprise plan customers
Ever tried dealing with noisy neighbours? Yeah, not much fun. You might have thought: “I would pay anything to have some peace and quiet.“
If you go Enterprise with Enterspeed, then you can. We've taken the first steps towards providing dedicated resources for our Enterprise plan customers.
As both we and our customers grow, a predictable processing speed is important for us.
By dedicating a slice of our processing layer to individual enterprise customers, we've effectively eliminated noisy neighbours for them.
fix Fixes and tweaks 🛠️
- The save schema shortcut (Ctrl + s) is available again.
- Source entities with null properties no longer cause NPE for subsequent ingests
…We have also added a bunch of features and fixes to our Umbraco Source connector – head over to the changelog to view more!
🤫 Teaser The Enterspeed CLI
A highly requested feature will soon see the light of day – the Enterspeed CLI.
Our skilled engineers have been working tirelessly on the first version of the Enterspeed Command Line Interface.
We’re really excited to share this with you all. The CLI will bring a whole new way of working with Enterspeed, by having it available via your favourite IDE.
Soon we will be letting the first few customers try out our beta, so we can get some feedback before releasing it.
If you’re interested in testing it out – feel free to drop us an email at email@example.com
Until next time 👋