Introduction
This release completes the rollout of Required Fields on Creation across the CRM — with required-field indicators, creation gating, and Settings configuration for Projects, Workforce, Opportunities, Contacts, and Companies — alongside sortable role columns in Reports and a round of fixes in CRM and Settings.
Power-Up Release
- Required Fields on Creation — Configurable, per entity — Admins can now define exactly which fields must be filled in before a new record can be created — including standard fields, financial fields, and required associations such as workforce roles — configured independently for Projects, Workforce members, Opportunities, Contacts, and Companies.
- Required Fields on Creation — Clear indicators, end to end — Users see required-field indicators throughout the creation flow: vacant role cards flag unfilled required associations, incomplete tabs and sections are visually marked, and a disabled Create button highlights that something required is still missing — so records can't be saved half-finished.
- Required Fields on Creation — Now in the Outlook Add-in — The same enforcement extends to records created from the Outlook Add-in, including required roles on Opportunities and required fields on new Contacts and Companies, so data stays complete no matter where a record is created.
Feature Drop
- Sortable role columns in Reports — Report columns for role-based associations (such as Architect or Client) can now be sorted, making it faster to organize and scan association-heavy reports.
Fix-It Release
- CRM
- Closing an association modal while an action is still processing no longer triggers a "can't close" warning as often; the modal now waits for the action to finish before closing.
- Settings
- Formula fields can no longer be configured as required on creation, preventing a setup that could block records from being saved.
Questions or Feedback
For questions or feedback regarding these changes, please contact our support team by logging a support ticket or visit our Help Center.
