<?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: Access feature class in same SDE database with different schema owner in Attribute Rules Questions</title>
    <link>https://community.esri.com/t5/attribute-rules-questions/access-feature-class-in-same-sde-database-with/m-p/1596681#M1722</link>
    <description>&lt;P&gt;&amp;nbsp;I believe the AR is executed by the Data Owner.&amp;nbsp; Does the Data Owner have permissions to that table?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 18 Mar 2025 17:30:18 GMT</pubDate>
    <dc:creator>MikeMillerGIS</dc:creator>
    <dc:date>2025-03-18T17:30:18Z</dc:date>
    <item>
      <title>Access feature class in same SDE database with different schema owner</title>
      <link>https://community.esri.com/t5/attribute-rules-questions/access-feature-class-in-same-sde-database-with/m-p/1596620#M1720</link>
      <description>&lt;P&gt;I am trying to create an attribute rule to populate a field with an ID attribute of an intersecting feature. My Arcade expression validates when I intersect with a feature class in the same database and with the same schema owner. In this case I am adding attribute rules to the sde.PWORKS.Sign feature class and getting attributes from the sde.PWORKS.Pole feature class. However when I try to intersect with a feature class in the same database with a different schema owner (sde.ENG.CityGrid) I receive an error that the CityGrid layer cannot be found.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Using the following to access the CityGrid layer:&amp;nbsp;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;var grid = FeatureSetByName($datastore, "sde.ENG.CityGrid", ["CITYGRID"], false);&lt;/P&gt;&lt;P&gt;Does $datastore only work if the feature class in the same database with the same owner? Is there an alternative way to access a feature class with a different schema owner?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Mar 2025 16:02:43 GMT</pubDate>
      <guid>https://community.esri.com/t5/attribute-rules-questions/access-feature-class-in-same-sde-database-with/m-p/1596620#M1720</guid>
      <dc:creator>Dennis1</dc:creator>
      <dc:date>2025-03-18T16:02:43Z</dc:date>
    </item>
    <item>
      <title>Re: Access feature class in same SDE database with different schema owner</title>
      <link>https://community.esri.com/t5/attribute-rules-questions/access-feature-class-in-same-sde-database-with/m-p/1596681#M1722</link>
      <description>&lt;P&gt;&amp;nbsp;I believe the AR is executed by the Data Owner.&amp;nbsp; Does the Data Owner have permissions to that table?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Mar 2025 17:30:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/attribute-rules-questions/access-feature-class-in-same-sde-database-with/m-p/1596681#M1722</guid>
      <dc:creator>MikeMillerGIS</dc:creator>
      <dc:date>2025-03-18T17:30:18Z</dc:date>
    </item>
    <item>
      <title>Re: Access feature class in same SDE database with different schema owner</title>
      <link>https://community.esri.com/t5/attribute-rules-questions/access-feature-class-in-same-sde-database-with/m-p/1597137#M1738</link>
      <description>&lt;P&gt;Yes, that was the issue. I gave the PBWORKS account view permissions on the dataset owned by ENG and the attribute rule verifies. Our user accounts have read access by default on both the public works and engineering data sets but didn't consider that our data owner accounts don't have that permission. Thank you for the help.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Mar 2025 15:44:38 GMT</pubDate>
      <guid>https://community.esri.com/t5/attribute-rules-questions/access-feature-class-in-same-sde-database-with/m-p/1597137#M1738</guid>
      <dc:creator>Dennis1</dc:creator>
      <dc:date>2025-03-19T15:44:38Z</dc:date>
    </item>
  </channel>
</rss>

