Now, this is something that I have never encountered before. It just started occurring over the weekend
I have a Section Access Script that looks like this:
LOAD text(USERID) as USERID, TEXT(PASSWORD) as PASSWORD, 'MSWBH\' & text(NTNAME) as NTNAME, LASTNAME, FIRSTNAME, IF(LEN(TRIM(ACCESS)) > 0,'ADMIN','USER') AS ACCESS, TEXT(GROUP) as GROUP, text(OMIT) AS OMIT FROM [..\..\..\Security.xlsx] (ooxml, embedded labels, table is Sheet1);
Directory; LOAD TEXT(GROUP) AS GROUP, ACCESS FROM [..\..\..\Security.xlsx] (ooxml, embedded labels, table is Sheet2);
The Group Info is as follows:
I use the group setup to hide certain fields from users from Group 1 that are included in the OMIT field.
In the app, I also hide certain charts by adding the condition "sum(ACCESS) >= 1" which means that only those users that belong to GROUP2 can view those charts. We use Publisher to distribute the documents. So, after I reload the publish the document, the app in the Source document looks accurate. It assigns the correct group to the correct user. ( I tested that by giving myself restricted access and I observed that I could see one row in the group table that had GROUP 1 AND 0).
However, when I look at it from Accesspoint, I see that everything that should be hidden is still visible. I also see in the table viewer that the group info has been reversed, i.e. GROUP 2 AND 1. That is the reason why the objects are not hidden, even though data reduction takes place successfully
I am clueless as to why the Publisher would change this on the fly.