<?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: Input Field Qlikview storing into database methodology in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Input-Field-Qlikview-storing-into-database-methodology/m-p/1245349#M394948</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As much as I would like to, its probably more effort for our business to acquire these extensions and go through the chains of compliance etc...etc...also mass distribution among users.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 13 Jan 2017 20:54:17 GMT</pubDate>
    <dc:creator />
    <dc:date>2017-01-13T20:54:17Z</dc:date>
    <item>
      <title>Input Field Qlikview storing into database methodology</title>
      <link>https://community.qlik.com/t5/QlikView/Input-Field-Qlikview-storing-into-database-methodology/m-p/1245347#M394946</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello All, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to figure out a good methodology in inputting Input Field Comments back into a database.&amp;nbsp; For a dashboard that will be used by multiple people at a given time there is a potential to have a dirty read and write.&amp;nbsp; Has anyone come up with any design that prevents dirty reads and writes?&amp;nbsp; Note I have a macro that writes the dimension and the comments into a database for storage. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Jan 2017 16:46:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Input-Field-Qlikview-storing-into-database-methodology/m-p/1245347#M394946</guid>
      <dc:creator />
      <dc:date>2017-01-13T16:46:08Z</dc:date>
    </item>
    <item>
      <title>Re: Input Field Qlikview storing into database methodology</title>
      <link>https://community.qlik.com/t5/QlikView/Input-Field-Qlikview-storing-into-database-methodology/m-p/1245348#M394947</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Maybe this one is useful: &lt;A href="https://community.qlik.com/docs/DOC-5970"&gt;SQL Writeback from QlikView extension object.&lt;/A&gt; And there are multiple commercial solutions available, too - it will save time, had support and will probably run more stable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Jan 2017 19:31:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Input-Field-Qlikview-storing-into-database-methodology/m-p/1245348#M394947</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2017-01-13T19:31:55Z</dc:date>
    </item>
    <item>
      <title>Re: Input Field Qlikview storing into database methodology</title>
      <link>https://community.qlik.com/t5/QlikView/Input-Field-Qlikview-storing-into-database-methodology/m-p/1245349#M394948</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As much as I would like to, its probably more effort for our business to acquire these extensions and go through the chains of compliance etc...etc...also mass distribution among users.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Jan 2017 20:54:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Input-Field-Qlikview-storing-into-database-methodology/m-p/1245349#M394948</guid>
      <dc:creator />
      <dc:date>2017-01-13T20:54:17Z</dc:date>
    </item>
  </channel>
</rss>

