idea Allow Registered Database Views As the Destination Table in Relationship Classes in Data Management Ideas https://community.esri.com/t5/data-management-ideas/allow-registered-database-views-as-the-destination/idi-p/1112224 <P>Allow the Destination table in a relationship class to be a registered database view. The relationship wouldn't support any features that a view would prohibit (no composite relationships, no message passing etc.) but could be used to link database view records to a parent feature or record in apps such as Field Maps.</P><P>The main use of this feature in my organization would be to create a view of an entire archive table or branch versioned table in the EGDB, register that view, then allow users to jump to a list of archived records directly from a feature in various apps. To my knowledge there is no consistent method of relating data in ArcGIS without a relationship class in the database and this seems more pragmatic than defining a new relationship type at the Server/AGOL/Enterprise level.</P> Thu, 27 Oct 2022 21:53:33 GMT DavidSolari 2022-10-27T21:53:33Z Support Relationship Classes on Database Views https://community.esri.com/t5/data-management-ideas/allow-registered-database-views-as-the-destination/idc-p/935873#M1786 <HTML><HEAD></HEAD><BODY><P>The Support for creating Relationship Classes on registred Database Views was dropped in ArcGIS &gt; 10.2.2. Please reactivate this Functionality in future Releases of ArcGIS.</P></BODY></HTML> Thu, 18 Jul 2019 10:35:29 GMT https://community.esri.com/t5/data-management-ideas/allow-registered-database-views-as-the-destination/idc-p/935873#M1786 ThomasJurk 2019-07-18T10:35:29Z Allow Registered Database Views As the Destination Table in Relationship Classes https://community.esri.com/t5/data-management-ideas/allow-registered-database-views-as-the-destination/idi-p/1112224 <P>Allow the Destination table in a relationship class to be a registered database view. The relationship wouldn't support any features that a view would prohibit (no composite relationships, no message passing etc.) but could be used to link database view records to a parent feature or record in apps such as Field Maps.</P><P>The main use of this feature in my organization would be to create a view of an entire archive table or branch versioned table in the EGDB, register that view, then allow users to jump to a list of archived records directly from a feature in various apps. To my knowledge there is no consistent method of relating data in ArcGIS without a relationship class in the database and this seems more pragmatic than defining a new relationship type at the Server/AGOL/Enterprise level.</P> Thu, 27 Oct 2022 21:53:33 GMT https://community.esri.com/t5/data-management-ideas/allow-registered-database-views-as-the-destination/idi-p/1112224 DavidSolari 2022-10-27T21:53:33Z Re: Allow Registered Database Views As the Destination Table in Relationship Classes https://community.esri.com/t5/data-management-ideas/allow-registered-database-views-as-the-destination/idc-p/1159100#M1824 <P>There is so much Esri functionality that needs to support database views.&nbsp; This is one of those things.</P> Tue, 29 Mar 2022 20:30:12 GMT https://community.esri.com/t5/data-management-ideas/allow-registered-database-views-as-the-destination/idc-p/1159100#M1824 AdamStewart 2022-03-29T20:30:12Z Re: Allow Registered Database Views As the Destination Table in Relationship Classes https://community.esri.com/t5/data-management-ideas/allow-registered-database-views-as-the-destination/idc-p/1331364#M2270 <P>We absolutely need this in order to not having to write view content back to a physical table.</P> Fri, 22 Sep 2023 07:55:27 GMT https://community.esri.com/t5/data-management-ideas/allow-registered-database-views-as-the-destination/idc-p/1331364#M2270 GillesLavandier 2023-09-22T07:55:27Z