Project filters can be set to include or exclude projects for users and/or expense types. Filters exclude by default and so the logic can be awkward. Filters use Tags
Before setting up a filter it is necessary to configure the project. The easiest way to do this is to use the User Sort keys in a project record.
Please note that in Expense the filter for USERSORT1 refers to the first user sort in the accounts called SortKey. Therefore, the numbers are out of sync as USERSORT2 in expense refers to USERSORT1 in the accounts.
Setting the Filter:
In the project record(s) to be filtered, enter the relevant value in the required sort field.
In expense, Settings, create a Tag Type for use in the filter and assign a tag to it with the text entered into the project.
Then create a Project Filter with the name of the Tag created above and set the logic as necessary.
Assign the filter to a User or Expense type via their record.
Example:
The project to be filtered has the value USERSORT1 in the second sort key field.
In Expense, there is a tag type called ProjectFilter and one active tag for that called USERSORT1.
The project filter called USERSORT1 has one operator based on that tag type as not equals User Sort 2 (see above)
Project filters can be set to include or exclude projects for users and/or expense types. Filters exclude by default and so the logic can be awkward. Filters use Tags
Before setting up a filter it is necessary to configure the project. The easiest way to do this is to use the User Sort keys in a project record.
Please note that in Expense the filter for USERSORT1 refers to the first user sort in the accounts called SortKey. Therefore, the numbers are out of sync as USERSORT2 in expense refers to USERSORT1 in the accounts.
Setting the Filter:
In the project record(s) to be filtered, enter the relevant value in the required sort field.
In expense, Settings, create a Tag Type for use in the filter and assign a tag to it with the text entered into the project.
Then create a Project Filter with the name of the Tag created above and set the logic as necessary.
Assign the filter to a User or Expense type via their record.
Example:
The project to be filtered has the value USERSORT1 in the second sort key field.
In Expense, there is a tag type called ProjectFilter and one active tag for that called USERSORT1.
The project filter called USERSORT1 has one operator based on that tag type as not equals User Sort 2 (see above)
Below is a summary of the settings and what effect they have:
Project Filter not equal:
user set
expense type not set
All expense types visible and filtered to the project only
user set
expense type unavailable for
All expense types visible and filtered to the project only
user set
expense type available for
Filtered expense type not visible others filtered to the project only
Project Filter equal:
user set
expense type not set
All expense types visible and filtered to exclude the project
user set
expense type not set
expense type visible and all filtered to exclude the project
user set
expense type unavailable for
expense type visible and all filtered to exclude the project