Winter '25 Release Breaks Org Shape with PersonAccount Feature Enabled

gabordemeter commented 1 month ago

Summary

Since the Winter '25 release, our scratch org creation process has encountered issues when using Org Shape with the PersonAccounts feature enabled. We recreated the org shape post-release, as usual, but scratch orgs created from this shape are not properly configuring Person Accounts. While the Person Accounts setting appears enabled, the necessary Person Account objects and record types are not created

Steps To Reproduce

Create a new Org Shape

sf org create shape --target-org my-prod

Use the following scratch org configuration file:


{
  "orgName": "Shape Scratch",
  "sourceOrg": "00D20000000XXXX",
  "features": [
    "PersonAccounts"
  ]
}

3.Run the following command to create a scratch org:


    sf org create scratch --definition-file config/shape-scratch-def.json --shape --alias shape1 --duration-days 1 --no-track-source --wait 20

The scratch org is created successfully, and the Person Account setting appears enabled in the setup, but the PersonAccount object and its record types are missing.

Expected result

Person Account enabled correctly when we create it from org shape.

Actual result

Person Account feature even though is enabled on UI, the object and recordtype not created as expected.

Additional information

When creating a scratch org without Org Shape from a config file, enabling the PersonAccounts feature, it works as expected, and Person Accounts are fully configured.

System Information

I tested the scratch org creation with your provided docker containers, in multiple versions:

github-actions[bot] commented 1 month ago

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

github-actions[bot] commented 1 month ago

Hello @gabordemeter :wave: It looks like you didn't include the full Salesforce CLI version information in your issue. Please provide the output of version --verbose --json for the CLI you're using (sf or sfdx).

A few more things to check:

Make sure you've provided detailed steps to reproduce your issue.
- A repository that clearly demonstrates the bug is ideal.
Make sure you've installed the latest version of Salesforce CLI. (docs)
- Better yet, try the rc or nightly versions. (docs)
Try running the doctor command to diagnose common issues.
Search GitHub for existing related issues.

Thank you!

pavel-ebury commented 1 month ago

I'm having the same issue after Winter'25 roll out on Saturday

github-actions[bot] commented 1 month ago

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.

yoanama commented 1 month ago

We are experiencing the same thing. Have raised a case with Salesforce but they had not been made aware of this issue yet. They are looking into it but if someone finds a solution, please let us know.

jonathankretzmer commented 1 month ago

From our experience this appears to be broader than just scratch org creation, we are seeing the same thing when building new validated unlocked package versions.

jonathankretzmer commented 1 month ago

Here is the issue logged on Salesforce: https://issues.salesforce.com/issue/a028c00000zi5J9/

jonathankretzmer commented 1 month ago

It looks like a patch is being rolled out to correct this issue, our package version creation is now working as expected.

forcedotcom / cli