T
Trutz-Sebastian Stephani
What was the idea of changing the Filter options for Views in PWA 2003 to the
new Filter dialog in PWA 2007? Easier Usability?
Because now I can't use filters with wildcards or the "contains" or "begins
with" Option for Fields with underlying LookUp Table.
Let's say I have an Outline Code with 4 different levels and 6 options for
every node in the tree. No I have to negate every tree node on every level
leading to a huge amount of "equals not to" conditions. In PWA 2003 I simply
could say Outline Code equals not "<node on level1 name>%". What to to do
now? Any changes planned?
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/communitie...11&dg=microsoft.public.project.pro_and_server
new Filter dialog in PWA 2007? Easier Usability?
Because now I can't use filters with wildcards or the "contains" or "begins
with" Option for Fields with underlying LookUp Table.
Let's say I have an Outline Code with 4 different levels and 6 options for
every node in the tree. No I have to negate every tree node on every level
leading to a huge amount of "equals not to" conditions. In PWA 2003 I simply
could say Outline Code equals not "<node on level1 name>%". What to to do
now? Any changes planned?
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/communitie...11&dg=microsoft.public.project.pro_and_server