7
Scratch orgs are intended to be throw-away and have a limited life span of at most 30 days. Instead of trying to re-use a scratch org you should throw it away and build a new one.
4
This is a bug I feel somewhere in the sfdx cli and one needs to bring it attention to Salesforce on this.
The following is a workaround that did actually work for me .
I created an application named 'case' in my scratch org
Run `sfdx force:source:pull.
Add the folder path of the application in .gitignore and in .forceignore files.
Note that with this ...
3
Could you try this configuration file (borrowed from answer in this post with updates on settings) :
{
"orgName": "Your Org Name",
"edition": "Enterprise",
"features": [
"Communities", "PartnerCommunity", "ForceComPlatform"
],
"settings": {
"communitiesSettings": {
"enableNetworksEnabled": true
}
}
}
3
It's undocumented but it is available as enableOotbProfExtUserOpsEnable property in the communities settings metadata as of v47 (Winter '20). If you select the Allow using standard external profiles for self-registration and user creation checkbox and then retrieve the settings metadata using this package
<?xml version="1.0" encoding="UTF-8"?>
<...
2
Well I resolved this issue uninstalling the last version (7) and moving back to de previous one (6).
In my case the npm uninstal cmd did not work because I installed it manually so i removed the whole package folders:
sudo rm -rf /usr/local/sfdx
sudo rm -rf /usr/local/lib/sfdx
sudo rm -rf /usr/local/bin/sfdx
sudo rm -rf ~/.local/share/sfdx ~/.config/sfdx ~/...
2
The Official documentation can be found here.
However
I haven't had much success getting the debugger to hit breakpoints in my actual commands. Even when I did get it to break, source-maps seemed to be way off.
To even get it to attach, I had to remove "localRoot": "${workspaceFolder}" from the launch.json config. Otherwise I would get an error when ...
2
You can change to any version you want by using the @version notation:
sfdx plugins:install sfdx-cli@7.26.0
(Or any other version).
Note that ordinarily there is some "gap" between the various version parts, and is not likely the issue. Normally, you'd upgrade/downgrade the entire salesforcedx package:
sfdx plugins:install salesforcedx@latest
Or
sfdx ...
2
I ran into this same error trying to update sfdx locally.
I think this is indeed an issue with the latest release of sfdx-cli on npm (version 7.30.11)
I thought running sfdx plugins:install salesforcedx would do the trick, but that updated the salesforcedx plugin to 47.3.6 (according to the npm listing for the salesforcedx plugin the released versions went ...
2
In your project configuration, you can specify a definitionFile for your second-generation package:
... A reference to an external .json file used to specify the features and org settings required for the metadata of your package, such as the scratch org definition.
Just like with a regular scratch org definition file, the definition for your 2GP's build ...
2
It may not be the best option but I put the responsibility on the developers to frequently retrieve all changes from the org they are working in and then pick out the admin changes that need to be merged into GIT. Illuminated Cloud’s retrieve and merge function make this really easy.
We also have admins consistently making changes in Prod. For example, ...
2
It's a known bug that hasn't been fixed, you can follow progress over here:
https://success.salesforce.com/issues_view?id=a1p3A000001SitrQAC
2
It doesn't look like you have git installed on your computer. Here's a link to the installation steps: https://git-scm.com/book/en/v2/Getting-Started-Installing-Git
1
On our product roadmap, we have plans to support installing and upgrading multiple packages in a single transaction.
Until that is available, would this multi-step process work for you?
1) Release Package A ver 1.1.0 that has both the methods - global static void doFoo() and global static void doFoo(String msg).
2) Release Package B ver 1.1.0 where doBar(...
1
As the documentation says, you can't use lightning:overlayLibrary in Lightning Out. You'd need to use your own. You might look at strike_modal instead. You'll need to create a component that will dynamically create the other components, and your dependency app must list all components that will be used dynamically.
1
You should use CreateSalesforceObject to create a task. Also you probably will need to lookup the user to create this task for, and will hence need RetrieveSalesforceObjects to get the ID
1
To avoid the error on running sfdx force:source:pull run the following query through the tooling API and delete any records it returns (easily done in Dev Console):
SELECT Id, MemberType, MemberName FROM SourceMember WHERE MemberType = 'Workflow'
If you have any workflow metadata which you need to retrieve then use sfdx force:source:retrieve to pull these ...
1
You have options for either of the 2 avenues you always have...Paid or free. It does seem the paid route would be the less scary option for someone not willing to do command line, but that depends on your team.
Buy a deployment tool
Many exist in this realm - gearset, autorabit, copado, clickdeploy, etc...
I can't speak to all of them, but some will make ...
1
You must use a Scratch org not a standard Sandbox.
System Requirements
Developer Hub-enabled org
Most recent stable version of Chrome, Firefox, Safari, or Edge web browser
Windows—Windows 7 (64-bit and 32-bit) or later
Mac—macOS 10.11 or later
Linux—Ubuntu 14.0.4 or later
Salesforce CLI
Reference
Local Development (Beta)
1
Currently, dynamic error message is not available in Salesforce.
Refer to this idea: https://success.salesforce.com/ideaView?id=08730000000IEYh
1
The -r or --instanceurl param is just supposed to point to the right endpoint environment. I don't think you can achieve what you're looking for within the CLI command itself.
Official Documentation for auth:web:login doesn't give URL param options as an example, nor suggests that this could be done
-r | --instanceurl INSTANCEURL
Optional
- The ...
1
Per Salesforce Support:
Meanwhile, you can include "FieldService" in the feature.
FieldServiceSettings is available via Metadata API and thence also in the settings portion of the SFDX config -
Try including fieldServiceOrgPref to true to actually activate the feature, while the feature's entry just makes it available.
The FieldService feature ...
1
In addition to identigral great answer, here is the corresponding code for scratch org creation (project-scratch-def.json)
"settings": {
"communitiesSettings": {
"enableNetworksEnabled": true,
"enableOotbProfExtUserOpsEnable": true
},
1
The sfdx structure is meant to be used in a repo. The folder structure is not uploaded to Salesforce during sfdx deployments, and thus cannot later be retrieved. You can deploy the same code to multiple orgs using sfdx, and can even push/pull from multiple scratch orgs, as the metadata is saved per org in the sfdx configuration files.
1
Assuming you have already set up Visual Studio Code and installed the necessary extensions:
It is as easy as right click the folder in VS Code to delete > SFDX: Delete From Project and Org
Note: If you accidentally renamed your LWC in VS Code and pushed it into your org (e.g. Renamed "LWC_Eample" to "LWC_Example"), the old LWC "LWC_Eample" will still be ...
1
If you try:
sfdx force:source:delete -m ApexClass:SomeClassName -r
sfdx force:source:push
You will indeed remove the class, but not its references (for instance, on profiles). Which means that the push will fail.
The best way to do this, it's to remove it on the org using the developer console. Then pull your changes into your repo.
1
The scratch-def.json file is necessary for Unlocked Packages. Features must be enabled in this file in order to create Unlocked Packages that depend on specific features. Eventually, you'll want to migrate your settings to the JSON file in order to produce Unlocked Packages to simplify deployments. Any features that can be set in this file should be. Not all ...
1
Unfortunately this is currently a bug in the Metadata API.
We've been talking about it for a while, and I currently have a Case open for it.
Please add your voice to the discussion on the Trailblazer Community on this thread, the more people asking for it, the more likely they fix it.
Create another case may help too.
[EDIT]: A Known Issue has been ...
1
Rather than try to research all these, just remove them from the profile XML, then re-deploy. This should fix the files without needing to use the UI. However, please note that some permissions may have been added by the Winter '20 update, and standard profiles cannot generally be modified in terms of system permissions. This is why most organizations opt to ...
Only top voted, non community-wiki answers of a minimum length are eligible
