Skip to Main Content
Update: This Suggestion Box has been migrated to The Network, Trimble's online user community and is now read-only. Please click the link to add a new idea, vote, or comment.
Created by Mercedes Green
Created on Jun 26, 2025

Hiding Fields on PCO should not alter calculations, cause errors or disable updates to Budget Screen

I brought this to support but I'm told it's classified as an enhancement request.

We wanted to simply the shear number of columns that appear on the PCO Items to only those we need to type into. If you hide the "Applied" column, which can't even be typed into, any amount you enter in Estimated or Proposed or Approved, will never hit your budget code as it keeps applied at zero.

ProjectSight's code and calculations should still work if we hide a column, but it appears you need to have it shown for the budget code to get updated.

  • Attach files
  • Mary Antonacci
    Mar 12, 2026

    The 'stop sign' on fields in a security role should remove from the UI view only, not Delete the field causing calculations not to work. There is no need for users to have access to fields they will not use.