New answers tagged

0

Disclaimer: I am part of the team building this free and open-source product. Orchestrating scratch org builds, specifically including creation, pushing source, setting passwords, assigning permission sets (via sfdx invocation), and opening the org is the raison d'etre of CumulusCI, Salesforce.org's build toolchain. CumulusCI is configured via a YAML file ...


2

The fastest quickest setup option, in my opinion, is going to be a native command line script for your system. This is what things like bash and PowerShell have been doing really well since the dawn of time. And all you need is essentially a text file with the right perms (sudo chmod u+x on the script in your Unix-based os or in PowerShell running Set-...


1

For our case it was necessary to compile the project with yarn, before linking it. 1 Install Yarn. 2 Open a commandline in the plugin folder 3 run yarn 4 run sfdx plugins:link .


0

I just tried the same plugin installation command: sfdx plugins:install @muenzpraeger/sfdx-plugin It appeared to do a number of steps that aren't showing in your screenshot. C:>sfdx plugins:install @muenzpraeger/sfdx-plugin This plugin is not digitally signed and its authenticity cannot be verified. Continue installation y/n?: y Finished digital ...


0

One of the reasons may be conflict in your aliases files. You can find following folder on your computer: %USERPROFILE%/.sfdx and find there file alias.json. There would be all your used aliases and you can investigate if you have any conflicts.


1

As per the error, it seems that Entitlement object is not recognized yet as a standard object. To fix this, ensure that Entitlement Management is enabled first in the target org before deploying the object metadata components.


Top 50 recent answers are included