Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
I need to limit the data for our users in my app. For this I use a landed "Orga" table that contains an "Org.-Nr". This number is linked to all tables to restrict the view accordingly.
An Excel table with the users and their "Org.-Nr" is imported via Section Access.
The access restrictions work very well.
But now I have the problem that after loading Section Access, the date is cut off and instead of, for example, 12/31/2025, only the data up to 08/15/2023 (today) is available.
I saw that there were already similar cases, but unfortunately I didn't get any further with the solution.
Do you have the time and inclination to help?
Here is the Section Access script:
ACCESS:
LOAD * INLINE [
ACCESS,USERID
USER,ENSE\qlik_user
];
JOIN
LOAD DISTINCT
Orga.OrgNr
RESIDENT Orga;
Concatenate(ACCESS)
LOAD DISTINCT
'USER' as ACCESS,
DOMAIN&"USERID" as USERID,
"Org.-Nr" as Orga.OrgNr
FROM [.../SECTION_ACCESS.xlsx]
(ooxml, embedded labels, table is Table1);
NoConcatenate
TMP:
LOAD
UPPER(TEXT(ACCESS)) as ACCESS,
UPPER(TEXT(USERID)) as USERID,
AUTONUMBER(UPPER(TEXT(Orga.OrgNr)), '%ACCESS') as %ACCESS
RESIDENT ACCESS;
DROP TABLE ACCESS;
SECTION ACCESS;
NoConcatenate
ACCESS:
LOAD *
RESIDENT TMP;
SECTION APPLICATION;
DROP TABLE TMP;
It sounds like there are no rows with these future dates associated with the Org Numbers in question. Since Section Access is effectively the same as applying a filter, this would result in those dates not being available if the Dates table is connected to the table containing the Org Numbers.
Hi,
the table Orga contains the Org-Nr as well as the date.
Like:
Org-Nr. Date
1000 01/01/2020
1000 01/02/2020
1000 ...
1000 12/31/2025
2000 01/01/2020
2000 01/02/2020
2000 ...
2000 12/31/2025
I found the solution. I have to insert the same MaxDate in all other fields that access the date. If everyone has the same date range, it works.