*.profile-meta.xml files are not pulled after object deletion

[sauloefo]

Summary

After custom object deletions in a scratch org, files related to profile are not updated by sfdx force:source:pull command.

Steps To Reproduce:

1. Create a new scratch org.
2. Open the new scratch org.
3. Create a new Custom Object.
4. Retrieve modified metadata with sfdx force:source:pull
5. Verify the profile files are referencing, for instance, the new custom object layouts.
6. In the scratch org, delete the created Custom Object
7. Retrieve the metadata using sfdx force:source:pull again

Expected result

The *.profile-meta.xml files doesn't contain any reference to deleted custom object assets.

Actual result

The *.profile-meta.xml files keeps references to deleted custom object assets. This will cause failure to any upcoming sfdx force:source:push execution.

Additional information

Created Object:

Retrieved metadata using sfdx force:source:pull

Retrieved metadata after custom object deletion.

Content of profile-meta.xml files after custom object deletion and pulling of scratch org source code.

ERROR: result of sfdx force:source:push -f into a new scratch org with the last pulled source code version:

SFDX CLI Version: sfdx-cli/6.50.0-9817aece8a (darwin-x64) node-v8.9.4

OS and version: darwin18 (MacOS Mojave)

[clairebianchi]

@sauloefo thank you for the feedback, we are aware of the issue and are planning to fix it in Summer '19, our internal work item is W-5234377. I will leave this bug open till we have made the change

[sauloefo]

@sauloefo thank you for the feedback, we are aware of the issue and are planning to fix it in Summer '19, our internal work item is W-5234377. I will leave this bug open till we have made the change

Hi Claire! Great to know it will be solved soon! If you believe this would be good for a first issue collaboration please let know. I'd be glad to help solve it.

[clairebianchi]

@sauloefo Thank you for the offer, but sadly this part of our codebase is not currently public.

[mshanemc]

Follow-up note--this isn't a problem with the pull command. It's a problem with SourceMembers for the profile not getting updated when the Object is deleted.

So that profile change from the deleted object won't show up in status and there's nothing on the server to pull.

And that's not going to be something the CLI team can fix. Created @W-10287607@ to get the server issues corrected.

➜  gh14 sfdx force:data:soql:query -t -q "select id, IsNameObsolete, MemberIdOrName, MemberName, MemberType, RevisionCounter from SourceMember"
ID                  ISNAMEOBSOLETE  MEMBERIDORNAME      MEMBERNAME           MEMBERTYPE    REVISIONCOUNTER
──────────────────  ──────────────  ──────────────────  ───────────────────  ────────────  ───────────────
0MZ0t00000PDzXZGA1  false           00e0t000000wnnnAAA  Admin                Profile       1
0MZ0t00000PDzXaGAL  true            00h0t000003gbMwAAI  Test__c-Test Layout  Layout        5
0MZ0t00000PDzXbGAL  true            01I0t000001qkK6EAI  Test__c              CustomObject  4
Total number of records retrieved: 3.
Querying Data... done

[github-actions]

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.

[RupertBarrow]

Hi @mshanemc , this bug is pretty frightening, especially since the issue is still open more than 1 year after you found the cause. When can we hope this to be fixed ?

[mshanemc]

I don't expect this one to get fixed. The more cases, the better chance.

[RupertBarrow]

Disappointing.
You should probably close this issue and mark it "Wont Fix".

[mshanemc]

If I close it here, it closes it in GUS (the internal tracking system) so I won't. Also, eternal optimist and all that.

[iowillhoit]

@RupertBarrow @sauloefo, unfortunately the linked issue was "nevered" as a "Bug without a Case" by the owning team. The best way for this to get fixed is to open a Support Case and link back to this Github Issue and also "W-10287607".
Closing this issue here.