<?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: Publish sde using view error - &amp;quot;feature selections are not supported&amp;quot; in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/publish-sde-using-view-error-quot-feature/m-p/334117#M18996</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Are you talking about a view or a spatial view?&amp;nbsp; Does it exist within the database or is it a query layer within the map document?&amp;nbsp; I'm guessing it's the former based on the error you mentioned.&amp;nbsp; I've always found that views or spatial views which exist inside of SQL Server or Oracle will always show an error when analyzing the map document in advance of publishing it as a service.&amp;nbsp; This is "expected" behavior and, even though it appears as though it's not supported by Esri, it works (for view-only purposes) when consuming via a map service.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 13 Dec 2013 00:46:37 GMT</pubDate>
    <dc:creator>WilliamCraft</dc:creator>
    <dc:date>2013-12-13T00:46:37Z</dc:date>
    <item>
      <title>Publish sde using view error - "feature selections are not supported"</title>
      <link>https://community.esri.com/t5/data-management-questions/publish-sde-using-view-error-quot-feature/m-p/334116#M18995</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I was under the impression that I could publish a service using a View. When I attempt this I get a high unresolved error, Code 00021, "Feature selections are not supported." This error code supposedly indicates that I have features selected, which I do not. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm using ArcMap 10.1 Standard and Server Standard. I've created a view using a large geodatabase and a table. I don't want to join and export them, because they are derived from separate sources, and each will be updated individually.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I would appreciate any advice.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- Jeri&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Dec 2013 00:01:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/publish-sde-using-view-error-quot-feature/m-p/334116#M18995</guid>
      <dc:creator>JeriLedbetter</dc:creator>
      <dc:date>2013-12-13T00:01:36Z</dc:date>
    </item>
    <item>
      <title>Re: Publish sde using view error - "feature selections are not supported"</title>
      <link>https://community.esri.com/t5/data-management-questions/publish-sde-using-view-error-quot-feature/m-p/334117#M18996</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Are you talking about a view or a spatial view?&amp;nbsp; Does it exist within the database or is it a query layer within the map document?&amp;nbsp; I'm guessing it's the former based on the error you mentioned.&amp;nbsp; I've always found that views or spatial views which exist inside of SQL Server or Oracle will always show an error when analyzing the map document in advance of publishing it as a service.&amp;nbsp; This is "expected" behavior and, even though it appears as though it's not supported by Esri, it works (for view-only purposes) when consuming via a map service.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Dec 2013 00:46:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/publish-sde-using-view-error-quot-feature/m-p/334117#M18996</guid>
      <dc:creator>WilliamCraft</dc:creator>
      <dc:date>2013-12-13T00:46:37Z</dc:date>
    </item>
  </channel>
</rss>

