<?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 DAML shared tab across multiple addins in ArcGIS Pro SDK Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-sdk-questions/daml-shared-tab-across-multiple-addins/m-p/1706051#M13556</link>
    <description>&lt;P&gt;Hello --&lt;/P&gt;&lt;P&gt;We are currently using the ArcGIS Pro SDK for Pro version 3.5, and had a question about creating a shared tab for use with multiple, independent addins.&lt;/P&gt;&lt;P&gt;By way of example, suppose I had two addins, called A and B.&amp;nbsp; They are both mutually exclusive and don't depend on each other.&amp;nbsp; Our end users may have both A and B installed, or they may have only A or only B, depending on their needs.&amp;nbsp; We would like to make it so that both A and B share the same tab in Pro's ribbon for easy access, but at the same time we would like to keep the two addins separated.&lt;/P&gt;&lt;P&gt;Currently, the only way that we know of to do this is to have a separate addin (let's call it Base) that defines a tab in its Config.daml file.&amp;nbsp; Both A and B then would list Base as a dependency in their own DAML files, with markup to insert each addin's buttons and tools onto that tab.&lt;/P&gt;&lt;P&gt;Is there a way to accomplish what I'm describing without having to have the separate Base addin?&amp;nbsp; Essentially, we'd like to do something similar to what CREATE TABLE IF NOT EXIST in SQL does:&amp;nbsp; create the table described or use it if it already exists.&amp;nbsp; If there's a option to do it programmatically as an alternative, that could work as well.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Matt Winslett&lt;/P&gt;&lt;P&gt;T-Kartor&lt;/P&gt;</description>
    <pubDate>Wed, 03 Jun 2026 18:08:14 GMT</pubDate>
    <dc:creator>mwinslett</dc:creator>
    <dc:date>2026-06-03T18:08:14Z</dc:date>
    <item>
      <title>DAML shared tab across multiple addins</title>
      <link>https://community.esri.com/t5/arcgis-pro-sdk-questions/daml-shared-tab-across-multiple-addins/m-p/1706051#M13556</link>
      <description>&lt;P&gt;Hello --&lt;/P&gt;&lt;P&gt;We are currently using the ArcGIS Pro SDK for Pro version 3.5, and had a question about creating a shared tab for use with multiple, independent addins.&lt;/P&gt;&lt;P&gt;By way of example, suppose I had two addins, called A and B.&amp;nbsp; They are both mutually exclusive and don't depend on each other.&amp;nbsp; Our end users may have both A and B installed, or they may have only A or only B, depending on their needs.&amp;nbsp; We would like to make it so that both A and B share the same tab in Pro's ribbon for easy access, but at the same time we would like to keep the two addins separated.&lt;/P&gt;&lt;P&gt;Currently, the only way that we know of to do this is to have a separate addin (let's call it Base) that defines a tab in its Config.daml file.&amp;nbsp; Both A and B then would list Base as a dependency in their own DAML files, with markup to insert each addin's buttons and tools onto that tab.&lt;/P&gt;&lt;P&gt;Is there a way to accomplish what I'm describing without having to have the separate Base addin?&amp;nbsp; Essentially, we'd like to do something similar to what CREATE TABLE IF NOT EXIST in SQL does:&amp;nbsp; create the table described or use it if it already exists.&amp;nbsp; If there's a option to do it programmatically as an alternative, that could work as well.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Matt Winslett&lt;/P&gt;&lt;P&gt;T-Kartor&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jun 2026 18:08:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-sdk-questions/daml-shared-tab-across-multiple-addins/m-p/1706051#M13556</guid>
      <dc:creator>mwinslett</dc:creator>
      <dc:date>2026-06-03T18:08:14Z</dc:date>
    </item>
  </channel>
</rss>

