Since reports will inevitably contain numerous errors, have a generated Report error list the user can reference to address the report errors.

There are Report fields, Inspection Events (S 6.2) in particular, that need to have error checking only for selected Inspection Types. for Example, there is no need to check Underwater inspection events on a Routine Inspection.

B.RT.H: Route Highway Mapping - make this item a multi select item. Currently for divided highways we enter them as two highway features and then need to create duplicate route RFGs for each one. We want to create one route RFG and select multiple...

5.2: Load Posting Status - make this section into regular fields, not an RFG. Instead, we will just overwrite the existing data like we used to in the NBI world. When submitting our data to the FHWA, Bentley will export the field history of these ...

It would be helpful if dropdown fields could also be calculated fields. This would help with SNBI implementation, since dual data collection will be necessary until after the March 2025 submittal. It would reduce the amount of effort required for ...

Dual entry of common fields required when creating a maintenance report.

It would be helpful to have the "in list" option when creating logic for error checks and calculated fields as well as the typical operators (>, <, contains, etc)

There is currently an advanced setting for Report Fields that allows the value to of a Report Field to be identical for the Asset and all its Reports. That option does not work for Maintenance Fields. It would be helpful for Maintenance Fields tha...

I need to be able to use the current date and current year for date calculations.

It would be useful to be able to update the CSJ field as part of a bulk workflow change, because often there are 80+ follow-up actions as part of a single contract.