topic Re: Data Reduction in Section Access problem with qlikview publisher in QlikView

Data Reduction in Section Access problem with qlikview publisher

jafari_ervin — Mon, 26 Jan 2026 18:19:17 GMT

Dears,

I have problem with section access with reduction,I explain my problem in different way:

1.I use sql table for section access the fields in table are Access , NTName, ReductionKey then I upper case all field with Upper function also I use Upper case fieldName.also I added qlikview service account to the NTName Field.

2.I use another sql table with field ReductionKey and AccessCode in section application.

Problem:

any user in the NTName can access the document via the access-point(when just check initial data.... and unchecked strict exclusion) but for all of them data reduce the reduction key for service user account.and fail to access the file error massage appear (when check both initial data... and strict exclusion)

But when I didnot publisher and use just qlikview server from user document tab then section access work correctly and data reduce for any user even I open the file via the open in server everything works correct.

My problem is with publisher .

Please help me.

thanks

Re: Data Reduction in Section Access problem with qlikview publisher

jafari_ervin — Sat, 29 Nov 2014 11:14:02 GMT

Dears,

I found my answer in another forum.I should access service user account to all filed.I did it with *.

best

Re: Data Reduction in Section Access problem with qlikview publisher

Thu, 19 May 2016 08:51:52 GMT

Jafari

can you please share your solution url pls

Re: Data Reduction in Section Access problem with qlikview publisher

Anonymous — Wed, 25 May 2016 09:20:30 GMT

Share the URL PLZZZZZZZ.

Re: Data Reduction in Section Access problem with qlikview publisher

oknotsen — Wed, 25 May 2016 09:40:58 GMT

Please use normal English instead of "plzzzzzz". This place is not your local high school.

Please post your own question in a new topic. This topic is over 18 months old. The OP might have moved on or changed email address or whatever. Whatever it is, he/she decided not to respond a week ago already to the same question.

Locked.