I'm trying to limit the display of master files, when a user creates a report using InfoAssist. I've seen the documentation, I've had our admin create the little file with the WHERE statement, I've tested it on my console per the documentation. Then, I put it into my group profile, and nothing happens. It still displays the files I don't want.

The documentation states that you can put it into edasprof.prf or site.wfs, and does not explicitly state that you can put it into a group profile, but since group profiles override edasprof, I figured it would work.

Here's what I did:

I set up a fex that says

WHERE NOT REMARKS LIKE '&No user access%';


My admin guy saved that as c:\wfexcludes\excludefiles.fex

I tried this and it worked:

SQL FMI SET FILECASE UPPER
TABLE FILE SYSTABLE
PRINT NAME REMARKS
-INCLUDE c:\wfexcludes\excludefiles.fex
END


So, in the group profile I put

-SET &&IBI_IF_FILE='c:\wfexcludes\excludefiles.fex';

just like the documentation said. No dice.

Any ideas?

This message has been edited. Last edited by: Kathleen Butler,

Hi Mike,

During some research on your issue I found another situation where the customer had the filter
incorrectly specified based on the HOLD file.

The WHERE was using equal to the HOLD and it should be not equal to the HOLD file to restrict the masters within InfoAssist.

The logic to build the HOLD file needed to be reversed. This way when a new
file is created, it will be allowed instead of restricted.

Here is a link that may also be helpful:
Limiting file display in InfoAssist with &&IBI_IF_FILE


Let us know if this helps you out.

Thank you for participating in the Focal Point Forum.

Kindest regards,
Tamra Colangelo
Focal Point Moderator - Information Builders Inc.
* Summit 2016 – June 13-17 in Reno, Nevada  - http://www.informationbuilders.com/events/summit

Tamra,

Thanks for your response, but I know my filter is working, because I tested it per the document you are referring to. My question is "will this work in a group profile" instead of putting it in edasprof or site.wfs. I only want the restriction to apply for a certain group of users.

Hello Mike,

This should definitely work for a Group Profile. You may want to check which profiles are being executed for a given user to ensure that your profiles are being properly read:

https://techsupport.informatio...om/sps/30293550.html

Please let me know if this helps.

Thanks,
Emily McAllister
Focal Point Moderator

Correct me if I'm off base here... but the Reporting server lets you define what Applications/Files a group can List / Read / Write etc... Why not use this approach? From the way I believe it should work as of 8.0.09 is that any group you create in the client will be in the Reporting Server. Why use a 7.7.03 technique when there is probably a better, less confusing way to do it in 8.1.05?

Also check the group profile for whether it is set to inherit or overwrite the edasprof. I think there are 4 choices...

quote:

Originally posted by Emily McAllister:
Hello Mike,

This should definitely work for a Group Profile. You may want to check which profiles are being executed for a given user to ensure that your profiles are being properly read:

https://techsupport.informatio...om/sps/30293550.html

Please let me know if this helps.

Thanks,
Emily McAllister
Focal Point Moderator

Hi, thanks. I know the profile is getting executed, because sets the APP PATH for that group, and that is working. I also tried to add this to my server profile, and that didn't work either, so I just opened a case.