New answers tagged

2

Please post code as text, not images. It's a good idea to pay close attention to those underlined squiggles you see in Visual Studio Code, here on line 5. It's telling you, as is Salesforce DX, that your scratch definition is not valid JSON. You have an extra layer of structure (curly brackets, defining a JSON object) around your settings. Remove the ...


4

We (Salesforce.org Release Engineering, where I work) use browser automation built on Robot Framework and Selenium to automate setup actions that are not Metadata API accessible. Robot covers both browser automation and automated UI setup for us. Robot is a keyword-based framework on top of Selenium that can make it easier to script the Salesforce UI. Since ...


0

Going off their Unsupported Metadata Types documentation The following components can’t be retrieved or deployed with Metadata API, and changes to them must be made manually in each of your organizations In your situation, I'd manually create the org-wide email addresses in your target org and then keep whatever you can in your normal deployment process (...


0

Please verify that you have Account.object xml file in your Source pulled from Production. When you pull Standard object, you have to specify them explicitly: sfdx force:source:retrieve -m CustomObject:Account or by Ant <types> <members> Account </members> <name> CustomObject </name> </types> So if you use just <...


0

For anyone coming upon this and developing second generation packages (2GP), orgPreferences has been deprecated. See this Salesforce blog post for information on enabling features in scratch orgs. The Metadata coverage report also has a handy scratch org settings generator.


1

For anyone struggling with the same above mentioned error while creating scratch org, I was able to create scratch org by downgrading my salesforcedx plugin version to : salesforcedx 47.18.0 (47.18.0) instead of latest at this moment(salesforcedx 48.5.1) sfdx plugins:install salesforcedx@47.18.0


0

Just in case to help anyone in the future, you also can obtain the package version ID installed in any org with: sfdx force:package:installed:list -u <alias|username> The output for a Nonprofit Success pack as example: ID Package ID Package Name Namespace Package Version ID Version Name ...


1

You cannot use scratch orgs with B2B CloudCraze because, as you noticed, the license is -unfortunately- not available in scratch orgs. So, you should use developer orgs or sandboxes for your development needs.


Top 50 recent answers are included