I suggest you ...

Ignore Unlocked Package Metadata In Comparisons

Currently, metadata from Unlocked Packages show up when comparing against an org. This leads to duplication of metadata in source control repositories (correct DX package repository and incorrect monolithic, "happy-soup" repository).

Using the Package2Member Object (Tooling API), it is possible to deduce whether or not a metadata item is part of an unlocked package. Therefore, it should be possible to ignore some or all unlocked packages (or any Package2 package), in a similar fashion to the way Gearset filters allow inclusion or exclusion of managed packages.

2 votes
Sign in
(thinking…)
Password icon
Signed in as (Sign out)

We’ll send you updates on this idea

Shawn W shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

2 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • Shawn W commented  ·   ·  Flag as inappropriate

    This overlap is creating big headaches for our team as we are transitioning from monolithic deployments to DX packages.

  • Shawn W commented  ·   ·  Flag as inappropriate

    I've tested this out by querying the Tooling API's Package2Member Object against specific metadata ID's. If the metadata is in a Package2 package, a single result is returned. If the metadata is not in any package, or even in a managed package, the query returns no results.

Feedback and Knowledge Base