We encountered unexpected behavior in BuildingConnected while archiving an opportunity.
An estimator was reviewing and cleaning up previously accepted opportunities and attempted to archive one specific job that was approximately two weeks old. During this action, a system prompt appeared, and the estimator proceeded under the assumption that only the selected opportunity would be archived.
After confirming the action, it became apparent that:
These opportunities were not intentionally selected and had to be manually un-archived afterward.
Reason for reaching out
From the user’s perspective, the archive action appeared to be applied to a single opportunity. The resulting behavior suggests that the archive function may be operating on a broader scope (such as a date range or global filter), but this was not clearly understood at the time of execution.
We are looking to understand:
This clarification is important so we can ensure consistent internal workflows and avoid accidental changes during routine opportunity management.
