Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I have read the requirements for section access to be upper, but that hasn't seemed to solve my problem.
below is my section access script:
Section Access;
LOAD * INLINE [
USERKEY, ACCESS, USERID, PASSWORD, NTNAME, %SECSOURCE
1,ADMIN, , ,DBG\CAMARK,*
2,ADMIN,ADMIN,ADMIN123,*
];
REM LOAD * INLINE [
USERKEY, OMIT
1, SECURITY_ID
1, CUSIP
1, DEAM_ID
];
LOAD upper(USERKEY),
upper(OMIT)
FROM Include\Security.xlsx
(ooxml, embedded labels, table is [Field Omits]);
Section Application;
LOAD * INLINE [
%SECSOURCE, SEC_SOURCE_ID
4,4
1,1
26,26
];
The second load (from the excel file), has the exact same data in the excel that it does in the REM'd INLINE statement. The fields are appropriately omitted when using the inline, but not when referencing the table from the excel. If I put the same load from excel statement after Section Application, i see the data in the data model, so QV does seem to be able to access the excel file correctly.
wow, and with that discovery, the problem is fixed. oi, stupid wild goose chases
Won't happen again in 2014 I guess.
Happy new year,
Peter