I do not agree what is shipped here. The idea is requesting something different. Three years later this option is still not correctly available in PowerWeb.

You want to be able to hide projects which have the wrong status, a wrong property value, no access. Also you should able to only show the selectable projects and not the sub folders within a project (if any).

PowerUser has all this.

I do not understand why this is still not available in PowerWeb.

Please reconsider.

Hi Coen, Thanks I found that you have to change the ProjectsFoldertree user preference to get this to work. This functionality is nowhere near what we had in the Power User client. This only allows a user to filter. The Power User functionality allowed you to control what a user could see and select.

Regards,

Marco Russian

Hi Frank, attached is a screenshot of the Filter when you create project copies, and want to filter for a specific project.

Regards, Coen

Hi Coen, How is this filtering done. I have just looked at 2021 and there is no filtering available. Also I noticed that you cannot nominate any columns of information either.

In Meridian 2020R2 we implement a filter on the project level to minimize the selection of projects. Users can now filter on all project levels i.e. project type, project name. discipline etc.

I do not understand why the so called same and better than PUC does not have this option.

Customers will continue using PUC and not the PWC.

Hi Chris.

Regarding your two questions:

1) From an administrator’s perspective, what ways would you envision that Meridian should 'restrict' or ‘filter’ the available listing of projects?

1-A) This is entirely dependent on the customer's needs and may vary between customers. It really should just be configurable.

2) Also, what would you want the user to see when selecting from a list of projects?

2-A) Again, this would depend on the customer's needs. The way the "Select Project" dialog works in PowerUser, along with the _BeforeExpandItem() event, is ideal.

Aaron

Customers do sort projects by buildings, project and project phase. A lot of customers do have more then 400 buildings with multiple documents.

The current solution shows only projects. This is unusable.

E.G. 400 Buildings with ten projects each = 4000 Projects

Those 4000 projects are just in one unsorted list and the users are able to place a document everywhere.

Thank you again for your suggestion.

When assigning documents to projects, there may be many factors that go into the filtering of potential projects. The event mentioned was intended to allow administrators to use VBScript to determine which projects to show the user.

When considering that the client is now a web client, the technical approach may be quite different. Development is working on ways that an administrator can "configure" a filter for potential list of projects rather than coding the filter instead of coding them.

To help further this effort, I’d like to pose two questions:

• From an administrator’s perspective, what ways would you envision that Meridian should 'restrict' or ‘filter’ the available listing of projects?

• Also, what would you want the user to see when selecting from a list of projects?

Chris Tsangarides
Product Manager
Accruent

Thank you for your suggestion.

Development is currently reviewing your idea. Stay tuned for updates.

Chris Tsangarides
Product Manager
Accruent