In this article, I will explain How to a Custom lookup table filter in Project Center in Project Server 2016 and Project Server 2013.
You might also like to read One or more code values in the lookup table either do not match the mask defined for the code or contain more than 255 characters
How to create a Custom lookup table filter in Project Center?
In Project Server 2016 / 2013, I have tried to use a contains, begin with as a Test condition within a filter for a project-level custom field that linked to a lookup table in Project Center view. but, It’s not working properly, and I got the below error:
One or more rows are invalid. Correct these errors and try again.
Even equal to test condition is working only with the exact value of this field.
One or more rows are invalid. Correct these errors and try again.
Unfortunately, it’s a limitation on the view filtering, where the Test list options (contains and begin with …etc) work only with text fields properly, so that you get this error “One or more rows are invalid. Correct these errors and try again“
Filter By “Contains” for a lookup table field in Project Server
To overcome this limitation and create a Custom lookup table filter in Project Center, you should follow the mentioned steps below:
Steps
- From PWA Settings > Below enterprise data.
- Click on Enterprise Custom fields and lookup tables.
- Click a New field with text type based on a formula.
- In formula section put the old custom field name that linked to a Lookup table.
- Publish your project to reflect the value of the old custom field to the new text custom field.
- You could now use all Test filter options like contains and begin with …etc to build your conditions and filter for lookup table without any kind of limitation.
Conclusion
To filter a lookup table field in Project Center, you can only use Equal to with the exact value, in this post we have learned how to create a custom lookup table filter in Project center to can filter with Contains and Begin with without facing this issue “One or more rows are invalid. Correct these errors and try again.“.
Applies To
- Project Server 2016.
- Project Server 2013.
- Project Server 2010.
Finally someone with an actual solution, thank you!