<?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 API should accept one endpoint definition when one endpoint already exists on the server. in Suggest an Idea</title>
    <link>https://community.qlik.com/t5/Suggest-an-Idea/API-should-accept-one-endpoint-definition-when-one-endpoint/idi-p/1988159</link>
    <description>&lt;P&gt;The QEM website allows the manual import of a task with one defined endpoint in the databases section. The API requires both endpoints to be defined, as such it is not able to import a task with only one endpoint defined.&lt;/P&gt;
&lt;P&gt;I would consider this a bug, as both methods should be consistent.&lt;/P&gt;
&lt;P&gt;This request is align the functionality of the QEM website and API clients, such that an import works for both manual and automation.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 03 Oct 2022 12:45:57 GMT</pubDate>
    <dc:creator>robert_craver</dc:creator>
    <dc:date>2022-10-03T12:45:57Z</dc:date>
    <item>
      <title>From now on, please track this idea from the Ideation por...</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/API-should-accept-one-endpoint-definition-when-one-endpoint/idc-p/2099892#M13167</link>
      <description>&lt;P&gt;From now on, please track this idea from the Ideation portal.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;A title="Link to new idea" href="https://ideation.qlik.com/app/#/case/281316" target="_blank" rel="noopener"&gt;Link to new idea&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Meghann&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;EM&gt;NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you &lt;STRONG&gt;only&lt;/STRONG&gt; see 1 tab with the login page, please try clicking this link first: &lt;STRONG&gt;&lt;A title="Authenticate me!" href="#" target="_blank" rel="noopener"&gt;Authenticate me!&lt;/A&gt;&lt;/STRONG&gt;&amp;nbsp;t&lt;/EM&gt;&lt;EM&gt;hen try the link above again. Ensure pop-up blocker is off.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Aug 2023 15:04:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/API-should-accept-one-endpoint-definition-when-one-endpoint/idc-p/2099892#M13167</guid>
      <dc:creator>Meghann_MacDonald</dc:creator>
      <dc:date>2023-08-02T15:04:16Z</dc:date>
    </item>
    <item>
      <title>Re: API should accept one endpoint definition when one endpoint already exists on the server. - Status changed to: Closed - Archived</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/API-should-accept-one-endpoint-definition-when-one-endpoint/idc-p/2099893#M13168</link>
      <description />
      <pubDate>Wed, 02 Aug 2023 15:04:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/API-should-accept-one-endpoint-definition-when-one-endpoint/idc-p/2099893#M13168</guid>
      <dc:creator>Ideation</dc:creator>
      <dc:date>2023-08-02T15:04:18Z</dc:date>
    </item>
  </channel>
</rss>

