Release 2023 - 9th of December

Welcome to the December release! We are very proud to present the new features, and we hope you will love them!

Let's begin with a short overview:

New webpart catalog

The Powell web parts are now organized into different categories, and their preview will help you to have an overview of all available features and choose the right one.


Just so you know, this change needs a sync spfx to be available on your site collection and is available only on Modern Online sites.

Ready to use web parts

The new webpart catalog also brings a set of ready-to-use web parts that can be chosen to quickly and easily build your page.


See the list of all ready to use web parts proposed by default: Ready to use webparts

Stay tuned! In the next release, you will be able to save your own ready-to-use webparts!

So that you know, this change needs a sync spfx to be available on your site collection and is available only on Modern Online sites.

Carpooling views

In the latest release, we proposed a new template for Carpooling usage. This template comprises pages displaying a list of rides and a detail page displaying information about a ride.

These two new views are now available in the search display catalog to be reused with your own content.


Carpooling - List


Carpooling - Details

New Christmas and New year's Eve seasonal theme

You can choose to embellish your intranet with two new themes and celebrate the end of the year :




New year's Eve


Taxonomy terms on search result

The taxonomy terms in search result views were displayed depending on the value selected during the contribution. In a multi-languages context, the language of the field could be displayed incorrectly (not in good language). 

That means a user will now see the taxonomy term in his language if the translation exists and not in the language of the contributor.

Button webpart

Access the new site creation wizard by creating a subsite through the button webpart.


My profile

Be informed of the completion of your profile with the indication of the percentage done.


Webpart configurations

Until now, we stored the webpart configuration in a dedicated list by referencing the page URL. In this way, if the URL of the page is changed, the configuration of the webpart can be lost and need to be saved again. 

This is why we changed how we store the webpart configuration by now referencing the page ID, which is unique and cannot be changed.

Was this article helpful?
1 out of 1 found this helpful