Unfortunately, Data Partitions do not work like that. (Also, do you want the user to be able to see a Request Area, fill out the Request, and then be told when they are trying to save that they cannot use that Request Area? Wouldn't it be better if they could not see the Request Areas you don't want them to use?)
Here is how Data Partitions work:
- Data Partitions are attached to one or more Roles.
- If a Role has access to a table (defined by Functional Access) and there are no Data Partitions defined in the Role for that table, then all rows in the table are available to that Role.
- If a Role has access to a table and there are Data Partitions defined in the Role for that table, then only a subset of rows in the table are available to that Role.
- The Data Partition defines the subset of rows based on the value(s) in one or more attributes in the table compared to fixed value(s) (literals) or an attribute directly related to the user's contact record.
Here is my recommended approach:
- Define a new Role (you can copy an existing Role) for the users of that particular department.
- In all the other Roles set a Data Partition for the Problem Category (pcat) table that allows view access to any Request Area except the ones you don't want them to use.
Cheers,
Lindsay