What’s happening?
When attempting to add a specific site component into a solution, additional unwanted site components (such as the community portal) are automatically being included. This behavior is unexpected and is causing issues, particularly when preparing for a production go-live.
Reason:
This occurs due to existing dependencies between the site components. Specifically, when adding one site component, another site component (e.g., community portal) is automatically included because the first site component references metadata from the second site.
Resolution:
To resolve this, ensure that the site component you are adding does not reference any metadata from the other site component (e.g., community portal). Removing these metadata references will prevent the unintended site component from being automatically included.