![](https://media.stonly.com/media/images/03b13671-e6a6-40ba-a4e3-04f6077c4511.png?s=854290966071ccc7d6de32fe969dbb958dd290ef1fbcbfd181220708c0e8add72d7104cfee00d3f40bb8d0fb5f2bfe3f4685f3096a59bee7c0164782e2cb3ea16fbab185cf297d0ed7200d1f8b9dd8da696ee6508c106d8c7ad1b14b1bb94030af9216c703150cfa2fa476efa3e8dfbe&w=1280&h=1440&auto=format)
![](https://media.stonly.com/media/images/03b13671-e6a6-40ba-a4e3-04f6077c4511.png?s=854290966071ccc7d6de32fe969dbb958dd290ef1fbcbfd181220708c0e8add72d7104cfee00d3f40bb8d0fb5f2bfe3f4685f3096a59bee7c0164782e2cb3ea16fbab185cf297d0ed7200d1f8b9dd8da696ee6508c106d8c7ad1b14b1bb94030af9216c703150cfa2fa476efa3e8dfbe&w=1280&h=1440&auto=format)
Why is a new version assigned during a smap update?
When updating, respectively distributing an update, the corresponding smap always receives a new version number. The reason for this is that the data table in the data input can change when a module is changed in the smap, so that the columns can no longer be displayed one below the other. Thus, one always receives a view of the data sets to a certain version.
A further reason is that one can return to a certain version or create a copy of a certain smap version at a later stage, if unwanted changes within the smap were made earlier. In this way, it is possible to see exactly which status a smap had at a particular version number.