<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Are table-only feature services designed to be published with branch versioning? in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/are-table-only-feature-services-designed-to-be/m-p/1705299#M103404</link>
    <description>&lt;P&gt;This behavior is intentional/expected in ArcGIS Pro, not a known defect based on current documentation scope.&lt;/P&gt;&lt;P&gt;In Pro, the contextual Versioning ribbon is surfaced for web feature layers that participate in branch versioning with Version Management enabled. A service that contains only tables (no geometry layers) can still expose a 'VersionManagementServer' endpoint, but Pro’s Versioning UI typically won’t light up unless there is at least one feature layer in the map/service.&lt;/P&gt;&lt;P&gt;References:&lt;BR /&gt;&lt;A href="https://doc.esri.com/en/arcgis-pro/latest/help/data/geodatabases/overview/manage-branch-versions.html" target="_blank"&gt;Manage branch versions | ArcGIS Pro documentation&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://doc.esri.com/en/arcgis-pro/latest/help/data/geodatabases/overview/branch-version-scenarios.html" target="_blank"&gt;Branch version scenarios | ArcGIS Pro documentation&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Workaround: publish/include at least one branch-versioned feature layer (geometry) in the same service (with Version Management enabled); then add the service to Pro and manage versions from that layer while editing/relating to the tables as needed.&lt;/P&gt;</description>
    <pubDate>Fri, 29 May 2026 19:46:49 GMT</pubDate>
    <dc:creator>Robert_LeClair</dc:creator>
    <dc:date>2026-05-29T19:46:49Z</dc:date>
    <item>
      <title>Are table-only feature services designed to be published with branch versioning?</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/are-table-only-feature-services-designed-to-be/m-p/1705266#M103400</link>
      <description>&lt;P&gt;I've been testing our ability to publish and work with branch versioned feature services in ArcGIS Pro (Pro v. 3.4; Enterprise v. 11.3), and when I started by publishing a table registered as branch versioned, I found that the contextual versioning ribbon would not appear when bringing the service into my map, even though the rest endpoint showed that a VersionManagementServer endpoint existed. When I tried a similar process with a point feature layer, the contextual versioning ribbon would appear successfully! After doing further testing, I've found that the versioning ribbon will appear after adding a service to the map as long as that service contains at least one layer with geometry, but it will not appear if the service doesn't contain any layers with geometry.&lt;/P&gt;&lt;P&gt;Is this behavior intentional, or is this potentially a bug that has been or has yet to be fixed?&lt;/P&gt;</description>
      <pubDate>Fri, 29 May 2026 17:51:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/are-table-only-feature-services-designed-to-be/m-p/1705266#M103400</guid>
      <dc:creator>KevinBoes2</dc:creator>
      <dc:date>2026-05-29T17:51:46Z</dc:date>
    </item>
    <item>
      <title>Re: Are table-only feature services designed to be published with branch versioning?</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/are-table-only-feature-services-designed-to-be/m-p/1705299#M103404</link>
      <description>&lt;P&gt;This behavior is intentional/expected in ArcGIS Pro, not a known defect based on current documentation scope.&lt;/P&gt;&lt;P&gt;In Pro, the contextual Versioning ribbon is surfaced for web feature layers that participate in branch versioning with Version Management enabled. A service that contains only tables (no geometry layers) can still expose a 'VersionManagementServer' endpoint, but Pro’s Versioning UI typically won’t light up unless there is at least one feature layer in the map/service.&lt;/P&gt;&lt;P&gt;References:&lt;BR /&gt;&lt;A href="https://doc.esri.com/en/arcgis-pro/latest/help/data/geodatabases/overview/manage-branch-versions.html" target="_blank"&gt;Manage branch versions | ArcGIS Pro documentation&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://doc.esri.com/en/arcgis-pro/latest/help/data/geodatabases/overview/branch-version-scenarios.html" target="_blank"&gt;Branch version scenarios | ArcGIS Pro documentation&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Workaround: publish/include at least one branch-versioned feature layer (geometry) in the same service (with Version Management enabled); then add the service to Pro and manage versions from that layer while editing/relating to the tables as needed.&lt;/P&gt;</description>
      <pubDate>Fri, 29 May 2026 19:46:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/are-table-only-feature-services-designed-to-be/m-p/1705299#M103404</guid>
      <dc:creator>Robert_LeClair</dc:creator>
      <dc:date>2026-05-29T19:46:49Z</dc:date>
    </item>
    <item>
      <title>Re: Are table-only feature services designed to be published with branch versioning?</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/are-table-only-feature-services-designed-to-be/m-p/1705428#M103412</link>
      <description>&lt;P&gt;Thank you for this background,&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/2538"&gt;@Robert_LeClair&lt;/a&gt;! This will be good for us to be aware of as we keep testing out use cases for branch versioning in our workflows.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jun 2026 13:18:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/are-table-only-feature-services-designed-to-be/m-p/1705428#M103412</guid>
      <dc:creator>KevinBoes2</dc:creator>
      <dc:date>2026-06-01T13:18:51Z</dc:date>
    </item>
  </channel>
</rss>

