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

Task update_admin_profile errors when the org has person accounts and a namespace #3544

Open
joeythomaschaske opened this issue Feb 22, 2023 · 2 comments
Labels
bug wi-created This issue is represented by a Work Item

Comments

@joeythomaschaske
Copy link

Describe the bug

When creating a new dev org using cci flow run dev_org --org dev I get the following error when the update_admin_profile task is ran as part of the config_dev flow

I see this might be an SFDX problem since it has been a problem for other people who are using a namespace and person accounts in a scratch org: https://salesforce.stackexchange.com/questions/206310/sfdx-personaccount-error-entity-of-type-recordtype-named-account-business-a

Reproduction steps

  1. update your orgs/dev.json org definition to have the PersonAccounts feature in the features array
  2. add namespaced: true under orgs/scratch/dev in your cumulusci file
  3. run cci flow run dev_org --org dev

Your CumulusCI and Python versions

CumulusCI version: 3.73.0
Python version: 3.11.0

Operating System

macOS 13.2

Windows environment

No response

CumulusCI installation method

pipx

Error Gist

https://gist.github.com/joeythomaschaske/34f0add83ccb9f41f1b88822881d5530

Additional information

No response

@davidmreed
Copy link
Contributor

I don't think it's exactly the same as the linked issue, but it's probably related.

The easy workaround is just to turn that task off (I'm not a big fan of what it does anyway). You'd do that by doing

flows:
    config_dev:
        steps:
            2:
                task: None

I think there is probably a way to configure the task with its own Record Type settings or a custom package.xml manifest to make the Metadata API happy, but I'm not sure exactly what that looks like. I will get a WI on our backlog but I can't make any promises about delivering a behavior change.

@davidmreed davidmreed added the wi-created This issue is represented by a Work Item label Feb 22, 2023
@davidmreed
Copy link
Contributor

Tracking as W-12589033

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug wi-created This issue is represented by a Work Item
Projects
None yet
Development

No branches or pull requests

2 participants