<?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>idea Allow tables to be stored into FeatureDataset in Data Management Ideas</title>
    <link>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idi-p/921909</link>
    <description>&lt;P&gt;Would be nice if tables could be stored into FeatureDatatset. Now, the only place to write them is the geodatabase root level... Some tables belong to a FeatureDataset logical theme and so have to be into it.&lt;/P&gt;</description>
    <pubDate>Wed, 24 Aug 2022 18:29:17 GMT</pubDate>
    <dc:creator>NicolasPy</dc:creator>
    <dc:date>2022-08-24T18:29:17Z</dc:date>
    <item>
      <title>Allow tables to be stored into FeatureDataset</title>
      <link>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idi-p/921909</link>
      <description>&lt;P&gt;Would be nice if tables could be stored into FeatureDatatset. Now, the only place to write them is the geodatabase root level... Some tables belong to a FeatureDataset logical theme and so have to be into it.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2022 18:29:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idi-p/921909</guid>
      <dc:creator>NicolasPy</dc:creator>
      <dc:date>2022-08-24T18:29:17Z</dc:date>
    </item>
    <item>
      <title>Re: Allow tables to be stored into FeatureDataset</title>
      <link>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/921910#M58</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;'tables' means naturally 'standalone tables'...

&lt;!-- content transformation source ID: 00a30000006XsVq --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Apr 2010 15:33:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/921910#M58</guid>
      <dc:creator>NicolasPy</dc:creator>
      <dc:date>2010-04-12T15:33:52Z</dc:date>
    </item>
    <item>
      <title>Re: Allow tables to be stored into FeatureDataset</title>
      <link>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/921911#M59</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;same as&amp;nbsp;&lt;A href="https://c.na1.visual.force.com/apex/ideaView?id=087300000008A49" target="_blank"&gt;https://c.na1.visual.force.com/apex/ideaView?id=087300000008A49&lt;/A&gt;

&lt;!-- content transformation source ID: 00a30000007ioOv --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Aug 2010 11:18:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/921911#M59</guid>
      <dc:creator>NicolasPy</dc:creator>
      <dc:date>2010-08-24T11:18:55Z</dc:date>
    </item>
    <item>
      <title>Re: Allow tables to be stored into FeatureDataset</title>
      <link>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/921912#M60</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Couldn't agree more.

&lt;!-- content transformation source ID: 00a30000008itr8 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Nov 2010 15:46:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/921912#M60</guid>
      <dc:creator>JoshWhite</dc:creator>
      <dc:date>2010-11-18T15:46:45Z</dc:date>
    </item>
    <item>
      <title>Re: Allow tables to be stored into FeatureDataset</title>
      <link>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/921913#M61</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&amp;nbsp;Also it would be nice to group tables somehow.. in some TablesDataset...

&lt;!-- content transformation source ID: 00a30000008lMM7 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Dec 2010 09:41:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/921913#M61</guid>
      <dc:creator>DusanOstojic</dc:creator>
      <dc:date>2010-12-13T09:41:51Z</dc:date>
    </item>
    <item>
      <title>Re: Allow tables to be stored into FeatureDataset</title>
      <link>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/921914#M62</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I agree.&amp;nbsp; This would eliminate permissions issues.

&lt;!-- content transformation source ID: 00a30000009C9wG --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Dec 2010 16:52:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/921914#M62</guid>
      <dc:creator>KATHERINEHADLER</dc:creator>
      <dc:date>2010-12-29T16:52:04Z</dc:date>
    </item>
    <item>
      <title>Re: Allow tables to be stored into FeatureDataset</title>
      <link>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/921915#M63</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;"&lt;SPAN&gt;&lt;SPAN&gt;If  it has no  geometry, it cannot participate in topological  relationships. And if it  cannot participate, it has no place being in a  Feature Dataset (FD)." (&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;A href="https://community.esri.com/" target="_blank"&gt;dananrg &lt;/A&gt;&lt;SPAN&gt;&lt;SPAN&gt;)&lt;BR /&gt;&lt;BR /&gt;i don't agree. Geodatabases (personnal, file or sde) works on DBMS theorys, including relation between tables and normalization (&lt;A href="http://en.wikipedia.org/wiki/Database_normalization" target="_blank"&gt;http://en.wikipedia.org/wiki/Database_normalization&lt;/A&gt;). Thus, a table has a place being in a fd...&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;

&lt;!-- content transformation source ID: 00a30000009FTjr --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jan 2011 10:59:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/921915#M63</guid>
      <dc:creator>NicolasPy</dc:creator>
      <dc:date>2011-01-31T10:59:42Z</dc:date>
    </item>
    <item>
      <title>store tables in dataset</title>
      <link>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/923354#M1948</link>
      <description>&lt;P&gt;I am going to make it simple because esri does not seem to listen to customers that have wanted this since the concept of Datasets was introduced.&lt;BR /&gt;&lt;BR /&gt;s. t. o. r. e.&lt;BR /&gt;r. e. l. a. t. e. d.&lt;BR /&gt;t. a. b. l. e. s.&lt;BR /&gt;i. n.&lt;BR /&gt;d. a. t. a. s. e. t. s.&lt;BR /&gt;!!!&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;-Tim&lt;/P&gt;&lt;!--  content transformation source ID: 087E00000005AD7  --&gt;</description>
      <pubDate>Tue, 13 Sep 2022 17:12:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/923354#M1948</guid>
      <dc:creator>TimLowrimore</dc:creator>
      <dc:date>2022-09-13T17:12:36Z</dc:date>
    </item>
    <item>
      <title>Enable to place tables in Feature Dataset</title>
      <link>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/1287709#M2193</link>
      <description>&lt;P&gt;Often it would be helpful to be able to add non-geometry table to Feature Dataset.&lt;/P&gt;&lt;P&gt;Not only because of "using Feature Dataset as a folder" but setting of permissions too and so on.&lt;/P&gt;&lt;P&gt;Some of "why" ideas here:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/t5/data-management-questions/tables-in-feature-datasets/td-p/404570" target="_blank"&gt;https://community.esri.com/t5/data-management-questions/tables-in-feature-datasets/td-p/404570&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 10 May 2023 14:33:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/1287709#M2193</guid>
      <dc:creator>DavidVelhartický</dc:creator>
      <dc:date>2023-05-10T14:33:16Z</dc:date>
    </item>
    <item>
      <title>Re: Allow tables to be stored into FeatureDataset</title>
      <link>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/1557608#M2451</link>
      <description>&lt;P&gt;Why is to such a fundamental thing to add? Either add folders oder let people add tables to feature datasets. When you have 3 tables and one featureclass all having relationship classes between each other you can really fast just give up using the Katalog view to find anything...&lt;/P&gt;</description>
      <pubDate>Tue, 12 Nov 2024 16:37:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/1557608#M2451</guid>
      <dc:creator>SRK</dc:creator>
      <dc:date>2024-11-12T16:37:12Z</dc:date>
    </item>
    <item>
      <title>Re: Allow tables to be stored into FeatureDataset - Status changed to: Closed</title>
      <link>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/1602992#M2505</link>
      <description>&lt;P&gt;Feature datasets are specific to storing spatial data that participates in a controller dataset. Non-spatial tables are not part controller datasets and therefore will not be part of feature datasets.&lt;/P&gt;&lt;P&gt;For more information on feature datasets and their intended use please see&amp;nbsp;&lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/data/feature-datasets/feature-datasets-in-arcgis-pro.htm" target="_blank"&gt;https://pro.arcgis.com/en/pro-app/latest/help/data/feature-datasets/feature-datasets-in-arcgis-pro.htm&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Apr 2025 21:22:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/1602992#M2505</guid>
      <dc:creator>ShannonShields</dc:creator>
      <dc:date>2025-04-04T21:22:21Z</dc:date>
    </item>
    <item>
      <title>Re: Allow tables to be stored into FeatureDataset</title>
      <link>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/1623406#M2537</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/1250"&gt;@ShannonShields&lt;/a&gt;&amp;nbsp;I'm wondering if there are any plans to let users compartmentalize geodatabase contents in the future? When you have a few hundred items in there, it's tough (especially for my lower-level users) to find the exact thing you want.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jun 2025 13:16:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/1623406#M2537</guid>
      <dc:creator>AlfredBaldenweck</dc:creator>
      <dc:date>2025-06-13T13:16:15Z</dc:date>
    </item>
    <item>
      <title>Re: Allow tables to be stored into FeatureDataset</title>
      <link>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/1623455#M2538</link>
      <description>&lt;P&gt;thinking workarounds?&lt;/P&gt;&lt;P&gt;for any "table" you want to include in a feature dataset,&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;give it a couple fields for x and y coordinates&lt;/LI&gt;&lt;LI&gt;calc them both to = 1&amp;nbsp;or even lat/long to "Null Island"&lt;/LI&gt;&lt;LI&gt;make it a point feature class and add it into the feature dataset&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;that will give you access to the "attribute table"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jun 2025 16:27:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/allow-tables-to-be-stored-into-featuredataset/idc-p/1623455#M2538</guid>
      <dc:creator>BillFox</dc:creator>
      <dc:date>2025-06-13T16:27:04Z</dc:date>
    </item>
  </channel>
</rss>

