<?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 Tips for QV Developing with AX 09 in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Tips-for-QV-Developing-with-AX-09/m-p/1058894#M466385</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Everybody,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I´m a QV Developer and the database of my company bases on Microsoft AX 2009.&lt;/P&gt;&lt;P&gt;Is there anyone who can give me some advise how a QV project should be constructed.&lt;/P&gt;&lt;P&gt;I know it's useful to split a analysation in writer, models and dashboards. My question is, at which state is it useful to join tables or to&lt;/P&gt;&lt;P&gt;generate transaction tables. Because in AX there are often tables which have similar fields, so you get often circle relations between your tables So what's your tip to avert circle relations and to bulid up a good analysation??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry for my bad english. I'm a bit rusty &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Feb 2016 11:41:18 GMT</pubDate>
    <dc:creator />
    <dc:date>2016-02-05T11:41:18Z</dc:date>
    <item>
      <title>Tips for QV Developing with AX 09</title>
      <link>https://community.qlik.com/t5/QlikView/Tips-for-QV-Developing-with-AX-09/m-p/1058894#M466385</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Everybody,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I´m a QV Developer and the database of my company bases on Microsoft AX 2009.&lt;/P&gt;&lt;P&gt;Is there anyone who can give me some advise how a QV project should be constructed.&lt;/P&gt;&lt;P&gt;I know it's useful to split a analysation in writer, models and dashboards. My question is, at which state is it useful to join tables or to&lt;/P&gt;&lt;P&gt;generate transaction tables. Because in AX there are often tables which have similar fields, so you get often circle relations between your tables So what's your tip to avert circle relations and to bulid up a good analysation??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry for my bad english. I'm a bit rusty &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Feb 2016 11:41:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Tips-for-QV-Developing-with-AX-09/m-p/1058894#M466385</guid>
      <dc:creator />
      <dc:date>2016-02-05T11:41:18Z</dc:date>
    </item>
    <item>
      <title>Re: Tips for QV Developing with AX 09</title>
      <link>https://community.qlik.com/t5/QlikView/Tips-for-QV-Developing-with-AX-09/m-p/1058895#M466386</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;See: &lt;A href="https://community.qlik.com/thread/204430"&gt;Tipps zur QV Entwicklung mit Microsoft AX 09&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Feb 2016 14:46:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Tips-for-QV-Developing-with-AX-09/m-p/1058895#M466386</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2016-02-06T14:46:02Z</dc:date>
    </item>
  </channel>
</rss>

