Deploying project to a new scratch org generate warnings for GlobalValueSet and fail to track them #2870
Labels
area:mdapi
This is an issue for MDAPI server side team.
bug
Issue or pull request that identifies or fixes a bug
investigating
We're actively investigating this issue
owned by another team
The Salesforce CLI team does not own this work but will pass on the information to the correct team.
validated
Version information for this issue has been validated
Summary
When deploying sfdx project with global value sets to a new scratch org, the command generate some warnings and the global value sets are not properly tracked in the local source tracking in
.sf/orgs/<org-id>/maxRevision.josn
.The warnings generated in the first code deployment to a new scratch org:
When trying to deploy again using
sf project deploy start
, the global value sets are listed as conflicts:At this stage, the source code tracking in
.sf/orgs/<org-id>/maxRevision.josn
has"lastRetrievedFromServer": null
for the global value sets:The conflict can be resolve by forcing a deploy with
sf project deploy start --ignore-conflicts
, and the source tracking is updated:The only clue I can find for this is in the global value set metadata documentation:
Steps To Reproduce
Use the following project: https://github.com/hagai-shatz/MyProject
sf org create scratch -f ./config/project-scratch-def.json --alias test --no-namespace
sf project deploy start -o test
and see the reported warningExpected result
First code deployment to the new scratch org to properly track the version of global value sets.
Actual result
Global value sets fail to be tracked in first deployment of the code.
System Information
Additional information
The text was updated successfully, but these errors were encountered: