Sometimes users have issues with their Projects View. For instance, the All active projects view displays only few projects and the Search In fields are not visible although the Search option is enabled. This is an example of a possible corrupted View: 



This is the correct view if the Search panel option is activated:



In other cases, an internal error appears when trying to display a specific Projects View. This is the relevant section of the error details:
 

com.idiominc.ws.storage.StorageException
(covers com.idiominc.ws.sql.WSSQLException
(covers com.idiominc.ws.WSLocalizableRuntimeException: projects.view.error.column.name.not.found
com.idiominc.ws.storage.filter.ProjectStorageFilterCriterion.validateCustomAttributeName(ProjectStorageFilterCriterion.java:192) at
com.idiominc.ws.storage.filter.ProjectStorageFilterCriterion.validateCustomAttribute(ProjectStorageFilterCriterion.java:98)

These issues can happen with any type of Projects view, including Projects assigned to me, All completed and canceled etc.

Important: this happens only in the Legacy (Classic) UI. It does not happen in the modern WorldServer UI.

Resolution: If the issue is related to Root Cause #1 where one of the columns enabled (project attribute) contains an apostrophe, the resolution is to remove that apostrophe from the attribute's name.

To do so, if you are a WorldServer Administrator, go to Management > Administration > Customization, select Attributes and open the Project attribute with the apostrophe in the external name and remove the apostrophe, for instance, rename it to Project creator email. Save your change. The affected user should then refresh his/her Projects page: the Search field will re-appear even if the column is enabled because the apostrophe has been removed. If the issue was an internal error, that error will no longer appear.

Workaround: If the attribute's name cannot be renamed, the affected user can simply work in the Modern User Interface where the issue does not happen even if the column with an apostrophe in its name is enabled.

If - for some reason - the user insists on working in the Classic/Legacy UI only, he/she can remove that column from the problematic View in the Modern UI first. Once done, go back to the Classic/Legacy UI and to the view that was causing the issue previously. Now the user should be able to load the Projects View that was previously causing an issue.



Resolution to Root Cause #2

If the issue is unrelated to the project attribute's name, sometimes the issue is related to Browser Cache. Try to log in to WorldServer with a different Browser. Does the issue still happen? If not, you know that it is not a WorldServer issue but rather a Browser Cache issue.  Try to clear the Cache of the Browser where you are having the issue. Or close that Browser, log in to WorldServer with a different Browser, and perform different Searches that you will then remove. Then log in again with the Browser where you were having issues. Very often the issue is then solved.

If the above actions do not help, the other workaround is to reset the user's profile in the WorldServer Database. As a DB Administrator, run this query

delete from configuration where name like 'profiles/username%'

making sure to replace the username with the actual affected user's WorldServer username.
After refreshing the Projects page, the user will find that now all display correctly. Note - however - that previously set Search filters will no longer appear and need to be re-set.

Root cause 1- A possible cause is that one of the enabled/visible columns corresponding to a project attribute contains an apostrophe in its name. For instance, it is called Project creator's email. If enabled, that column causes the issue with the Search field disappearing or with the internal error appearing. This happens only in the Legacy User Interface. It does not happen when using the new WorldServer User Interface: the apostrophe in the attribute name does not cause any issue there.

Enabling that column in the Legacy/Classic UI works at first, but once you navigate away from it and then want to go back, the issue will happen when loading the previous view.





Root cause 2- A previous Search in the Projects page has not cleared correctly and somehow the View has not refreshed. This happens sporadically and rather rarely. So far, RWS Support has not been able to reproduce the behaviour.

Relevant articles:

How to reset a user's profile in the Database to fix possible View issues in WorldServer and in Transport
WorldServer - after selecting the view "all completed and cancelled jobs" in the Background Jobs page, the page hangs Cannot display the list of background jobs anymore