You need to make new relationships when loading the data into a Qlikview report.
In the QVD's the data is only stored for further usage ...
Each Qlikview report has it's own cloud of data, and it is not always necessary to maintain the complete Navision child-parent structure, since you don't always have to have all data between ...
Sometimes you need to let go the ' original ' way of thinking in database relationships!! Qlikview also can't handle all types of relations a normal database can handle (think of circular references etc).
there is another NAV Connector "NAV2QLIK" for QlikView from QlikView Solution Provider prisma informatik GmbH located in Germany.
"The preparation and connection of ERP data from Microsoft
Dynamics NAV into QlikView usually means a tedious and time consuming task to
To simplify this process and to reduce the preparatory work
to a minimum, prisma informatik has developed the NAV2Qlik Toolbox. On the part
of users, neither profound QlikView knowledge nor elaborate support by the
internal IT department is necessary during the ETL process. The NAV2Qlik Toolbox comes with the N2Q Script Generator, which generates the
required QlikView Scripts for data modeling automatically. Further components
are the N2Q Grouping Function and the N2Q Templates, which provide various options
for interface design in QlikView.
Especially the customizations within their ERP data are
particularly valuable for users of BI software. For this reason and unlike
other connector solutions, NAV2Qlik delivers no pre-built script, but can
generate the QlikView data model automatically direct from the specific NAV environment.
That way, NAV2Qlik enables the transfer of any
custom-built extensions and modifications within Microsoft Dynamics NAV - no matter how
individualized the database is. A separate number range without modifying
standard objects allows a conflict-free integration into the ERP environment."