Hello,
I’m trying to publish a branch-versioned feature service to consume it from an app, and my question is whether it can point to a specific version instead of default
Thanks in advance!,
Dolores S.
Solved! Go to Solution.
Hello,
You can also try using the gdbVersion parameter (I assume the Branch widget and field map versioning settings use this parameter internally).
For example, you can add this parameter to each layer of your web map:
Or directly in the REST URL when adding the service (https://serverName.esri.com/server/rest/services/serviceName/FeatureServer/4?gdbversion=versionName)
You can refer to this post : https://community.esri.com/t5/arcgis-enterprise-questions/use-branch-version-in-map-viewer/td-p/1146...
In Experience Builder, if you use the branch version widget, you can also set the version in the URL parameter :
This can be configured using the Versions setting in the Field Maps app. If you are using Experience Builder you can control this using the Branch Version widget. If you are creating your own custom JavaScript or runtime web app this is also possible but obviously requires customization.
The service itself cannot be locked to a specific version, but some applications allow you to lock a user into a specific version in the service.
Hello,
You can also try using the gdbVersion parameter (I assume the Branch widget and field map versioning settings use this parameter internally).
For example, you can add this parameter to each layer of your web map:
Or directly in the REST URL when adding the service (https://serverName.esri.com/server/rest/services/serviceName/FeatureServer/4?gdbversion=versionName)
You can refer to this post : https://community.esri.com/t5/arcgis-enterprise-questions/use-branch-version-in-map-viewer/td-p/1146...
In Experience Builder, if you use the branch version widget, you can also set the version in the URL parameter :