Key Concepts of Opportunity Management V2
Opportunity Management V2 connects Baucore’s Project object to standard Salesforce Opportunities, so a sales team that already works in Opportunities gets an accurate, always-current view of a project without duplicating data entry. This page covers the concepts that make the automation predictable; setup steps live in the Getting Started and Setup Options articles.
The bidirectional loop
Two things create the other automatically:
- Creating a Participant with a Role in the configured “auto-create roles” list creates a matching Opportunity for that Account, linked to the Project. (“Our Company” / My Company participants are always excluded.) If an Opportunity for that Account already exists on the same Project, roles are merged onto it instead of creating a duplicate. The new Opportunity’s Name is auto-generated as
Project Name - Account Name, truncated to 120 characters, and its Account is set from the Participant. Close Date is determined in this order: (1) the Project field mapped as “Project End Date,” if that mapping exists and the Project has a non-null value in it; (2) a per-Project number of days to close, if one is set; (3) otherwise, the org-wide default number of days (configured in settings) added to today’s date. - Creating an Opportunity with a Role set, and assigned to a Project (via BC Project Match), creates a matching Participant. No duplicate is created if one already exists with the same Account + Role.
Contact Roles on the Opportunity and Contacts on the Participant sync the same way, in both directions.
Active Opportunities follow Project Phase
Each Project Phase has a list of relevant Participant Roles (configured in Considerations for Opportunity Management). As a Project moves through phases, only the Opportunities whose Role matches the current phase’s relevant roles stay active — the rest go inactive and drop out of pipeline calculations, without being deleted. Moving “City Tower” into the Design phase, for example, activates its Architect and Building Owner Opportunities while the rest go inactive, and moving it further along reverses that as different roles become relevant.
An Opportunity can carry more than one Role when the same Account has multiple Participant records (with different Roles) on the same Project — that Opportunity stays active as long as any of its roles matches the current phase’s relevant roles.
Participant status drives Opportunity stage
| Participant Status | Buyer? | → Opportunity Stage |
|---|---|---|
| Won | Buyer | Closed Won |
| Won | Not Buyer | Indirect Closed Won |
| Won for Competitor | — | Closed Lost |
| Lost | — | Cancelled |
Stage mapping per status is configured by an admin in Baucore Admin → Opportunity Management → Stage Settings; a Project Phase change re-evaluates Stage and Forecast Category on every related Opportunity.
Field synchronization
- Reflect change on all opportunities — propagates a synced field edit to every related Opportunity, active or inactive.
- Respect Record Access — when on, sync only touches Opportunities the current user can read and edit, silently skipping the rest.
donotoverrideflag on an individual Opportunity excludes just that record from Amount sync.- Project Probability = 0 propagates to related active Opportunities; Project Probability = Null disables the sync instead of propagating a blank.
Lead conversion
Converting a Lead that is itself a Participant doesn’t create a duplicate Opportunity — whichever Opportunity results from the conversion (or from the auto-create-roles rule, if conversion doesn’t create one) is reused and linked back to the Project.
Related
- V2 — Multiple Opportunities for each Project
- Considerations for Opportunity Management
- Participant Management