I've encountered something puzzling that i can't find an answer for. I have an app which loads perfectly fine when editing but fails when setup as a task. Appears to have something to do with with the QVD actions, either store or load. Other apps without QVD's work fine as a task. The actual QVD is being updated, so i don't think it is security related - if it successfully saved it should be able to load. I've attached the script log. Appreciate any and all help!
Load Distinct 'ADMIN' as ACCESS, 'BSG\SVC-GER-BUS001' as USERID, UPPER(LOCATION_NAME) as LOCATION_NAME from [lib://QlikExcel/standardcosts.QVD](QVD);
Store Costs into [lib://QlikExcel/standardcosts.QVD];
Section Access is something that is imposed by the app when providing data to the end user - the way I think about it is that the server uses section access details to apply filters and the present the resulting subset of data to the end user as though the other data didn't even exist. (I'm not saying this is technically correct, it's just a way of conceiving what's happening)
It wouldn't normally be involved in the creation of qvd files. For example in a typical ETL scenario you might have the first app(s) to extract the data from source (eg your Costs SQL query) and save as a qvd. The second app(s) might apply any transformations using the qvds and saving transformed qvds. The third app(s) load those transformed qvds, apply section access and present to the user. The section access list itself might be generated during the first or second stages but the actual application (ie the "Section Access;" part of a load script) would only be used in the third layer apps.
It's probably not an issue, but in a load script with section access I tend to build all the data model first, then the at the end have the "Section Access;" followed by a minimal "Section Application;" which binds the user list to the data model.
