Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
hi,
I have an awfully big problem it is that I create a loop and I would like to eliminate it
the problem is that v_beleinfo 100 and vBeleg info 300 must be connected to the calendar and e_belgpos
I notice the two tables look quite similar. What if you concatenate the 100 and 300 tables into one and distinguish the two by adding a new field field called "Beleinfo type" with the valie 100 or 300?
" differentiated them by adding a new field named "Beleinfo Type" with a value of 100 or 300?"
and how to do it I am new in qlik and do not know all the functions yet?
Like this
BelegInfo
LOAD *,
100 as BelegInfoType
FROM V_BelegInfo100;
CONCATENATE (BelegInfo)
LOAD * ,
300 as BelegInfoType
FROM V_BelegIngo300;
Maybe this article by @chrislofthouse: Qlik Sense Data Modelling: Concatenate vs Link Tables in Qlik, can be a good read for you.
when I put the tables together it showed me this
and that is not true
.In tables 100 and 300 I use where:
V_beleg100 where V_beleg100.company=100
V_beleg300 where V_beleg300.company=300
the probllem is that the table with 100 has to have data only for the company 100 and the table with 300 has to have data from 300 the problem is that I can't connect them together because there are gaps like on the above screen
It is hard to understand your gaps without more info, but if you choose use the concatenation technique then you can probably share some of the dimensions between the data sets as well by renaming them.
Beleg:
LOAD
V_beleg100.company as company,
V_beleg100.wunchtermin as wunchtermin,
V_beleg100.versand as versand,
V_beleg100.menge as menge
etc...
FROM V_beleg100;
CONCATENATE (Beleg) LOAD
V_beleg300.company as company,
V_beleg300.wunchtermin as wunchtermin,
V_beleg300.versand as versand,
V_beleg300.menge as menge
etc...
FROM V_beleg300;
The problem is that I cannot connect these tables together and they need to access the calendar.
it's supposed to look like this but it creates a loop and doesn't display all the data
Have you considered the linked table approach in the blog post i linked to earlier.
Maybe it could be a way to go?