Users need a 'universal' widget that can be visible in every PlantSight project the user has access to, to show all the forms/IRS that are active for the user. This needs to be fed from all Plantsight projects.

Inability to bulk UPDATE items without specialized scripts and the API. If you need to change a field on 25 items, you are clicking ~75-100 times. This quickly becomes untenable. Inability to 'round trip' to excel (via CSV). Related to #1, you can...

There is no indicator showing that a file is out of date compared to the file in the Share.

Deleting a file is very frustrating. The only way I have managed to be able to delete any file is as follows: Update share. Import the file. Delete the file. This can only be done 1 file at a time.

We would like the ability to be able to manually select which classes to view in the Tag Browser tree from a list of all available classes, regardless of whether or not there are any active records in the database for a particular class.

We would like to have the option to display the actual property name rather than the property display label as the column alias in the Tag Browser results. This will help us in creating custom queries to know which properties to reference. Example...

When colors are not specified in data visualization, PS defaults the color to the same shade of red. Suggest for the system to use different shades of colors to visualize/group objects easily

When using a visual filter with the same color for two different attributes, the results show's only one attribute in the legend. However, at results both attributes should be availble in legend of visual filter. Please attached refrence info for ...

Equipment items on a P&ID will have a label directly under or close to the graphics and another label that is at the top or bottom of the sheet. Can we highlight the graphics and labels on the P&ID but just zoom to the graphics when a tag ...

We need to see a report that shows the status of acquired data. The ability to set the status of a tag to ignore will be required for the aggregation report to be useful. For instance, P&ID segments should be ignored as they are not tagged ite...