Duplicate Check
Availability
✅
❌
From
January 25
The duplicate check functionality helps identify duplicate metadata components across your Salesforce project. This analysis is crucial for maintaining clean code organization and preventing conflicts in your deployment process.
Overview
Duplicate checking scans your project's metadata components and identifies:
Components that exist in multiple packages
Components in aliasified packages
Components in unclaimed directories (not associated with a package)
How It Works
The duplicate checker:
Scans all specified directories for metadata components
Creates a unique identifier for each component based on type and name
Identifies components that appear in multiple locations
Provides detailed reporting with context about each duplicate
Configuration
Duplicate checking can be configured through several flags in the project:analyze command:
Key Configuration Options
--show-aliasfy-notes
Show information about aliasified packages
true
--fail-on-unclaimed
Fail when duplicates are in unclaimed packages
false
Understanding Results
The duplicate check provides three types of findings:
Direct Duplicates: Same component in multiple packages
Aliasified Components: Components in aliasified packages (typically expected)
Unclaimed Components: Components in directories (such as unpacakged or src/temp) not associated with packages
Sample Output
Understanding Indicators
The analysis uses several indicators to help you understand the results:
❌ Indicates a problematic duplicate that needs attention
⚠️ Indicates a duplicate that might be intentional (e.g., in aliasified packages)
(aliasified) Marks components in aliasified packages
(unclaimed) Marks components in unclaimed directories
Best Practices
Regular Scanning: Run duplicate checks regularly during development
Clean Package Structure: Keep each component in its appropriate package
Proper Package Configuration: Ensure all directories are properly claimed in sfdx-project.json
Documented Exceptions: Document cases where duplication is intentional
Common Scenarios and Solutions
1. Legitimate Duplicates
Some components may need to exist in multiple packages. In these cases:
Use aliasified packages when appropriate
Document the reason for duplication
Consider creating a shared package for common components
2. Unclaimed Directories
If you find components in unclaimed directories:
Add the directory to sfdx-project.json
Assign it to an appropriate package
Re-run the analysis to verify the fix
3. Aliasified Package Duplicates
Duplicates in aliasified packages are often intentional:
Used for environment-specific configurations
Different versions of components for different contexts
Not considered errors by default
Integration with CI/CD
When integrating duplicate checking in your CI/CD pipeline:
Configure Failure Conditions:
Generate Reports:
Review Results:
Use generated reports for tracking
Address critical duplicates
Document accepted duplicates
Troubleshooting
False Positives
Verify package configurations in sfdx-project.json
Check if components should be in aliasified packages
Ensure directories are properly claimed
Missing Components
Verify scan scope (package, domain, or path)
Check file permissions
Validate metadata format
Last updated