How to Set-up a Parent-Opportunity and Sub-Opportunity Auto-Update Linkage in CRMOD

The EMEA Instancein in our FYA Production Pod is set up so the end-users create a Parent Opportunity at an early project stage and this is treated as the primary opportunity all
throughout. The requirement is that the EMEA end-users need to create sub-opportunities from these Parent Opportunities wherever there is a requirement to quote, moving forward.

The issue here is that CRMOD doesn’t allow for any electronic passage (or linkages) of data between Parent Opportunities and Sub-Opportunities. As such, when there’s only a single Sub-Opportunity, the end-user has to maintain (or re-enter) key fields such as Sales Stages, win %, expected order date and order value hence duplication of effort.