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

MDAPI Error: Unknown user permission: CreateContentSpace #7

Open
paulie4 opened this issue Apr 24, 2020 · 1 comment
Open

MDAPI Error: Unknown user permission: CreateContentSpace #7

paulie4 opened this issue Apr 24, 2020 · 1 comment

Comments

@paulie4
Copy link

paulie4 commented Apr 24, 2020

I just created a new Test/Demo SF org, and when I ran initExistingOrg.sh, I got the following errors:

=== Component Failures [1]
TYPE   FILE                               NAME   PROBLEM
─────  ─────────────────────────────────  ─────  ───────────────────────────────────────────
Error  app-config/profiles/Admin.profile  Admin  Unknown user permission: CreateContentSpace

ERROR running force:mdapi:deploy:  The metadata deploy operation failed.
Job ID | 0Af5w00000U6fL1CAJ
MDAPI PROGRESS | ████████████████████████████████████████ | 1/1 Files
Job ID | 0Af5w00000U6fLGCAZ
SOURCE PROGRESS | ██████████████████████████████████████░░ | 20/21 Files
TYPE   PROJECT PATH                                            PROBLEM
─────  ──────────────────────────────────────────────────────  ───────────────────────────────────────────
Error  force-app/main/default/profiles/Admin.profile-meta.xml  Unknown user permission: CreateContentSpace
ERROR running force:source:push:  Push failed.

That in turn also caused the sfdx force:apex:execute -f config/create-demo-data-setup.apex call (in dataInit.sh) to fail with this error:

 ▸    ERROR: Line: 12, Column: 1
 ▸    Variable does not exist: HcDemoPack_DataSetup
ERROR running force:apex:execute:  Line: 12, Column: 1
Variable does not exist: HcDemoPack_DataSetup

To fix it, I edited mdapi-source/app-config/profiles/Admin.profile to remove the CreateContentSpace <userPermissions> and manually re-ran the remaining commands.

jrattanpal added a commit that referenced this issue Apr 24, 2020
@jrattanpal
Copy link
Collaborator

Thanks for reporting this. I have committed this change. d6d0939

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants