Hi Jens,

The protocol function version allows us to select which version to set as the active one on that DataMiner. Only that active version would be shown in other cube components e.g. the service definition editor. Moreover, this active version would be guarded so deleting or deactivating the active protocol function version would come with a due warning.

Uploading protocol function file using the original function file with updated version but with the same name would indeed not pass the cube validation checks. Renaming the function file to create a new protocol function version would indeed be the easiest workaround.

Please consider creating a feature suggestion if uploading a new protocol function version should behave the same as with uploading a new protocol version.

Do note that uploading system function with same name would work from 10.2.3 on though, see DataMiner ReleaseNotes.

Kind regards