<?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: Unknown search command 'return' in Security</title>
    <link>https://community.splunk.com/t5/Security/Unknown-search-command-return/m-p/69612#M2275</link>
    <description>&lt;P&gt;update ping &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 02 Jul 2013 08:15:19 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2013-07-02T08:15:19Z</dc:date>
    <item>
      <title>Unknown search command 'return'</title>
      <link>https://community.splunk.com/t5/Security/Unknown-search-command-return/m-p/69610#M2273</link>
      <description>&lt;P&gt;When a query with 'return' command is run by a non admin user, it throws the error&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Unknown search command 'return'
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Has anyone encountered this and found a fix for this permission issue?&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jun 2013 07:44:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Unknown-search-command-return/m-p/69610#M2273</guid>
      <dc:creator>Parameshwara</dc:creator>
      <dc:date>2013-06-20T07:44:49Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown search command 'return'</title>
      <link>https://community.splunk.com/t5/Security/Unknown-search-command-return/m-p/69611#M2274</link>
      <description>&lt;P&gt;Hi Parameshwara&lt;/P&gt;

&lt;P&gt;update on this error:&lt;BR /&gt;
the command 'return' is in the search app, so every user-role or app who likes to use the 'return' command, needs read access to the search app.&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jun 2013 07:54:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Unknown-search-command-return/m-p/69611#M2274</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2013-06-20T07:54:42Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown search command 'return'</title>
      <link>https://community.splunk.com/t5/Security/Unknown-search-command-return/m-p/69612#M2275</link>
      <description>&lt;P&gt;update ping &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2013 08:15:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Unknown-search-command-return/m-p/69612#M2275</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2013-07-02T08:15:19Z</dc:date>
    </item>
    <item>
      <title>Re: Unknown search command 'return'</title>
      <link>https://community.splunk.com/t5/Security/Unknown-search-command-return/m-p/539653#M12086</link>
      <description>&lt;P&gt;Thanks for this tip.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I encountered the error message&amp;nbsp;&lt;STRONG&gt;Unknown search command 'predict'&lt;/STRONG&gt; in a panel that used the predict command from the MLTK. The origin of the problem was the same - my user did not have access right to the Search and reporting app. This is strange, since I did not think that app would be involved at all.&lt;/P&gt;</description>
      <pubDate>Fri, 12 Feb 2021 09:26:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Unknown-search-command-return/m-p/539653#M12086</guid>
      <dc:creator>BernardEAI</dc:creator>
      <dc:date>2021-02-12T09:26:58Z</dc:date>
    </item>
  </channel>
</rss>

