Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception on force:org:beta:create when providing objectSettings section #1526

Closed
jonathankretzmer opened this issue May 18, 2022 · 9 comments
Labels
bug Issue or pull request that identifies or fixes a bug

Comments

@jonathankretzmer
Copy link

Summary

When using the command force:org:beta:create to create a scratch org, it will fail

Steps To Reproduce:

Repository to reproduce: forcedotcom-issue-scratchOrg-objectSettings

  1. Run command sfdx force:org:create --definitionfile config\project-scratch-def.json --durationdays 2 -w 30, passes
  2. Run command sfdx force:org:beta:create --definitionfile config\project-scratch-def.json --durationdays 2 -w 30, FAILS.

Expected result

I expect that the CLI should work for both the create and beta:create commands.

Actual result

sfdx force:org:create creates a scratch org as expected

sfdx force:org:beta:create Fails with error message:

ERROR running force:org:beta:create:  A scratch org was created with username [email protected], but the settings failed to deploy due to:
Invalid fullName, must end in a custom suffix ( for ex. __c )

If I remove the objectSettings the beta:create command works.

System Information

{
        "cliVersion": "sfdx-cli/7.150.0",
        "architecture": "win32-x64",
        "nodeVersion": "node-v16.15.0",
        "pluginVersions": [
                "@dxatscale/sfpowerscripts 13.0.15",
                "@oclif/plugin-autocomplete 0.3.0 (core)",
                "@oclif/plugin-commands 1.3.0 (core)",
                "@oclif/plugin-help 3.3.1 (core)",
                "@oclif/plugin-not-found 1.2.6 (core)",
                "@oclif/plugin-plugins 1.10.11 (core)",
                "@oclif/plugin-update 1.5.0 (core)",
                "@oclif/plugin-warn-if-update-available 1.7.3 (core)",
                "@oclif/plugin-which 1.0.4 (core)",
                "@salesforce/lwc-dev-server 2.11.0",
                "@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)",
                "alias 2.0.0 (core)",
                "apex 0.11.0 (core)",
                "auth 2.0.2 (core)",
                "community 1.1.4 (core)",
                "config 1.4.6 (core)",
                "custom-metadata 1.1.0 (core)",
                "data 0.6.15 (core)",
                "generator 2.0.0 (core)",
                "info 2.0.0 (core)",
                "limits 2.0.0 (core)",
                "org 1.12.1 (core)",
                "salesforce-alm 54.3.0 (core)",
                "schema 2.1.0 (core)",
                "sfdmu 4.14.3",
                "sfdx-cli 7.150.0 (core)",
                "sfdx-ext 0.0.55",
                "sfpowerkit 4.2.8",
                "signups 1.0.0 (core)",
                "source 1.9.7 (core)",
                "telemetry 1.4.0 (core)",
                "templates 54.6.0 (core)",
                "trust 1.1.0 (core)",
                "user 1.7.1 (core)"
        ],
        "osVersion": "Windows_NT 10.0.22000"
}

Additional information

The use of beta commands is due to a plugin that we are using that references the underlying SFDX core lib and not the CLI directly.

Related issue:
dxatscale/sfpowerscripts#942

@jonathankretzmer jonathankretzmer added the investigating We're actively investigating this issue label May 18, 2022
@github-actions
Copy link

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.

@iowillhoit
Copy link
Contributor

Hey @jonathankretzmer, thank you so much for the reproduction repo 🎉 I was able to reproduce this issue as well. I'll get a ticket created and we'll get it sorted out. Thanks for trying out our beta commands!

@iowillhoit iowillhoit added bug Issue or pull request that identifies or fixes a bug and removed investigating We're actively investigating this issue labels May 18, 2022
@uip-robot-zz
Copy link

This issue has been linked to a new work item: W-11163191

@dieffrei
Copy link

FYI @iowillhoit we also got the same issue.

@domrycz
Copy link

domrycz commented May 23, 2022

Hey @iowillhoit , any idea when this will be fixed? It's very painful issue for us.

@ruslan-kurchenko
Copy link

I have the same issue, any news about a solution?

@ppeersgi
Copy link

ppeersgi commented Jun 7, 2022

We are running into the same problem. Would be good to have a solution for this.

@dieffreys-angel
Copy link

Yup, this issue is very problematic. Solution is strongly needed.

@maggiben
Copy link
Contributor

Hello @dieffreys-angel @ppeersgi @ruslan-kurchenko @jonathankretzmer Can you please try the latest-rc a solution was deployed last RC release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue or pull request that identifies or fixes a bug
Projects
None yet
Development

No branches or pull requests

10 participants