If you have opened the Download Center recently, you may have noticed that the version numbers look different. Employee Directory went from 6.1.7 to 26.10.5, List Filter Online now reads 26.10.13, Smart Search 26.10.9. Nothing broke and nothing was skipped: starting in October 2026, all Vitextra products for Microsoft 365 share one versioning scheme.

Why we changed it

Every product used to have its own numbering, started at a different time and moved at its own pace. A number like 6.1.7 next to 4.0.3 or 1.3.7 told you nothing about which product was updated last, or whether the version on your tenant was a month old or two years old. The first question in almost every support request was "which version do you have?", and the answer rarely helped on its own.

How to read the new numbers

The format is year.month.build:

  • 26 — the year the release was built (2026)
  • 10 — the month (October)
  • 5 — the sequence number of the build within that month

So 26.10.5 is the fifth build released in October 2026. Comparing versions is now trivial: 26.10.5 is newer than 26.9.2, and anything that starts with 25 is at least a year old. You can see at a glance when the version on your site was built, without opening a changelog.

Which products are affected

The scheme applies to every product for Microsoft 365: Announcements Carousel, Employee Details, Employee Directory, List Filter Online, My Tasks, Organizational Chart, QR Code Generator, Questions & Answers, Quick Poll, RSS Reader, Smart Search and Smart Tiles — and to all new products from now on. It does not apply to the legacy products built for on-premises SharePoint Server — Document Auto Title, List Filter, Number Generator, Quick Filter and Short URL. They keep their current version numbers.

Where you will see the version

  • the Download Center and every product's changelog page
  • the app listing in Microsoft AppSource
  • the web part itself: the About section of the property pane shows the installed version

What it means for you

Nothing changes in licensing or in the way you update. Your licenses stay valid, the update procedure is the same, and the changelog continues as before — only the numbers are easier to read. If you compare versions in your own documentation or scripts, keep in mind that the new numbers are always greater than the old ones, so "newer is bigger" still holds.

A mapping of old to new version numbers for every product is in the Knowledge Base: KB10319. Vitextra Product Versioning: How to Read Version Numbers.

Vitextra versioning version numbers year.month.build SharePoint Online web parts Microsoft 365 a

Share