M
Michael Trilling
I have discovered a very unusual situation when creating a Filter. Although
the Filter is correctly defined and can be successfully applied, when the
project is saved to the server, a filter design error message pop-up is
displayed:
This is not a valid operator.
Click either Add or Or in the list, and then press Enter.
This makes completely no sense. If the filter is good enough to save and
use, then the project should be perfectly fine to save to the server. Not
only that, if there are enough filters exhibiting this condition, sequential
pop-ups are displayed, eventually causing the MS Project application to crash.
It appears that the condition that causes this anomaly to occur is related
to using the "parenthesis" option of the filter where a group of field tests
can be separated from another group of field tests with an "extra row" that
contains only an And or Or. The evaluation of the individual expressions
takes place before the result is used to evaluate the overall expression.
When a "group" of field tests contains only one field test separated by
another "group" of field tests containing only one field test using a
"parenthesis And", the error message is displayed when the project is saved.
For example:
Field1 equals ABC
and
Field 2 equals Orange
and
Field 3 equals George
or Field 3 equals Mary
causes the error but
Field1 equals ABC
and Field 2 equals Orange
and
Field 3 equals George
or Field 3 equals Mary
does not.
the Filter is correctly defined and can be successfully applied, when the
project is saved to the server, a filter design error message pop-up is
displayed:
This is not a valid operator.
Click either Add or Or in the list, and then press Enter.
This makes completely no sense. If the filter is good enough to save and
use, then the project should be perfectly fine to save to the server. Not
only that, if there are enough filters exhibiting this condition, sequential
pop-ups are displayed, eventually causing the MS Project application to crash.
It appears that the condition that causes this anomaly to occur is related
to using the "parenthesis" option of the filter where a group of field tests
can be separated from another group of field tests with an "extra row" that
contains only an And or Or. The evaluation of the individual expressions
takes place before the result is used to evaluate the overall expression.
When a "group" of field tests contains only one field test separated by
another "group" of field tests containing only one field test using a
"parenthesis And", the error message is displayed when the project is saved.
For example:
Field1 equals ABC
and
Field 2 equals Orange
and
Field 3 equals George
or Field 3 equals Mary
causes the error but
Field1 equals ABC
and Field 2 equals Orange
and
Field 3 equals George
or Field 3 equals Mary
does not.