report filter problem???

You want to do <>*DEMO & <>*STAFF

Yours didn't work because of this:

Say the salesperson is NAVDEMO. The first part of your filter, <>*DEMO returns false. The second part returns true.

Given that you are working with a custom built report - have you checked if there is any code in the report itself that applies filters to the Sales Person field? If so that could be overwriting your filter entered at run time.

Another issue I've seen in the past is that there are multiple data items used in a report and selectively some filters may get passed between them. Is there anything like this happening?

I know I've had problems where sometimes when I set a filter it actually looks for the * as a literal * and not a wild card. I can't remember exactly what I did to make it do so or how I fixed it, but I know it was just playing with the syntax. Maybe that's what is going on.

how many different types of <something>Staff or <something>Demo do you have?

losing the wild card would help

<>MYSTAFF&<>MYDEMO&<>YOURSTAFF&<>YOURDEMO

If you want these salesperson accounts with DEMO & STAFF fitered out in more that just this instance..say they are not actually regular sales people then it might be easier to add a field to the salesperson/purchaser table.

Such as a boolean called DEMO-STAFF where you can have it checked off.
Then in your report or any future reports you can check the table the set the filter DEMO-STAFF = no.

I thought that filter did work with SQL but not on native. :-k

Yeah that <> & * don't get along too well

One of these has to work

SETFILTER(Code, '<>*DEMO')

SETFILTER(Code, '<>*%1', 'DEMO');

I think the second one is more likely. There's only so many ways to set a filter.

I have been able to set filters like the ones described on a built in Navision report. Specifically the item list report. I don't know why yours are not working.

You shouldn't have to do a work around, but you might have to. I guess you could try to set the filter in code in the onpredataitem trigger. I would do it on the first lines, that way you can tell if there might be any code that is changing the filters at run time.

If the report is always going to use this filter that's what you should do anyway. If it is not you could add a checkbox to the request form that tells the report to set this filter with code.

Best of luck.