Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Please see attached file for all the tables and fields.
MARGIN_FACT and POSITION_FACT are concatenated.
I need to produce a table with the following fields:
- Exhange
- Contract Code
- Contract Description
- Aggregate Quantity
- Initial Margin
All this data comes from multiple tables which are linked in a complex way (you can see in the attached file).
I am trying to write the LOAD code to load all the needed fields so that I would be able to create the straight table. However, I tried many ways but there's always some problem, either a field is not showing or showing wrong data.
Please could anyone give me any advice.
Now every time I try to reload, I get the following error message:
Server Deployment Compatibility Warning
Internal inconsistency, type D, detected.
If this application is deployed on a server, the server will restart with the message above written to the event log.
Please contact QlikTech support for further assistance.
Even i had the same issue the thing is
first u need to avoid any sysnthetic keys it had
second if ur using more if conditions on the front end u may end endup getting
third it depends on how many records were present .
if ur datmodel is not properly designed u will get this type of error or ur running short of memory.
if the ram on ur desktop is less like 2gb then also u will get this ...
How would I avoid the syn keys? I think it might be one of the problems as I usually get the error after it starts creating them.
The number of records from one table is about 3mln, that's the highest, from other tables it's only about 15,000 records.
It used to be fine, no errors or problems when reloading the data and it just suddenly started for some reason
can u post the sample of the file like datamodel image..
I am not sure if you can see, but there are loads of syn keys. And this does not include all the tables, some more will have to be added later. Any ideas how to get rid of them?
Sorry for the quality, for some reason the picture saved differently than it looked on the screen.
Just figured out, that I might be getting this error because of licensing issues.
can you comment the fields which are on dimensions
or try to use a
autonumber hash( cal date,exchange , participatio......) as linked_key
after making this on every table then comment all the fields which are on dimenion side..
and try to get the star schema..
can u please attach a sample of qvw.. with limited rows
i am going to try this method :
autonumber hash( cal date,exchange , participatio......) as linked_key
just one question, would i create this key in multiple tables and give it the same name? or would the key name have to be different for all the tables?
i.e. cal date, exchange - linked key
cal date, exchange, participation - linked key 2
OR
cal date, exchange - linked key
cal date, exchange, participation - linked key
i am a complete newbie to this, sorry for asking too many questions
FIRST IDENTIFY WHAT ALL THE COMMON FIELDS YOU HAVE IN THE TABLES.
SEE WHAT MAKES THE SYSNTETIC KEY. TRY TO MAKE ALL THE FIELDS OF SYNTHETIC KEY AS LINKED KEY..
IF YOU STILL NOT FOLLOW POST AN SAMPLE FILE.