New answers tagged deployment
1
If you're using a Scratch Org, just force:source:pull, and the related profile settings will be retrieved.
If you're using a non-Scratch Org (Developer, Sandbox), retrieve the fields and profiles in one command:
sfdx force:source:retrieve -m CustomField:Opportunity.CustomField__c,Profile
That said, you should probably consider moving to Permission Sets (and ...
2
I was able to fix this pressing Setup -> Company Information -> Match Production Lcienses.
After pressing this button, Manage Sandboxes permission is available now.
2
OK I figured it out on Mac OSX. For a single file -p works as follows:
sfdx force:source:deploy -p "force-app/main/default/layouts/Snapshot__mdt-Snapshot Layout.layout-meta.xml"
However, for multiple files with your -p argument, you need to surround each filename with escaped double quotes as follows:
sfdx force:source:deploy -p """...
0
You can use ANT/workbench to retrieve the custom Settings metadata and make changes before deploying it to the destination.Please find the package.xml to retrieve the custom setting below:
<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
<members>...
0
We need to make changes as below:
1.Seems like you made changes to the retrieved .xml file incorrectly where you might have entered the details twice.Please check the example for more details.
2.If you are trying to create the customSetting using Metadata directly then I would suggest you to check the tags which should be given some value.So,I would suggest ...
1
I had the same issue with forceCommunity:themeProfileMenu
https://trailblazers.salesforce.com/answers?id=9064S000000CmW5QAK. It appeared that I had 2 theme layouts which contained forceCommunity:themeProfileMenu. Initially I updated pages that used the "Default" theme layout with the new Customized User Profile component but the error persisted. ...
0
Deploying Quick action through Changeset is not possible.
ref: https://developer.salesforce.com/forums/?id=906F0000000B59KIAS
You can use ANT tool else you need create it manually in target environment.
0
You can't currently get these details via SOQL. Instead, as sfdcfox answered, you can use the checkDeployStatus Metadata API to get this data.
Examples of calling this from Apex:
public void checkDeployStatus(Id deployRequestId) {
HttpRequest req = new HttpRequest();
req.setHeader('Authorization', 'Bearer ' + UserInfo.getSessionID());
req....
1
You shouldn't be trying to package profiles in Unlocked Packages. Salesforce has recommended that you use Permission Sets instead. This is even recommended in the trailhead project Create Permission Sets for Unlocked Packages. Permission Sets cover all the problems you're having.
0
Please make sure that you project-scratch-def.json have CustomerCommunityPlus elements.
Since you included CustomerCommunityPlus, it'll add one license in your scratch org.
{
"orgName": "Org_Name",
"edition": "Enterprise",
"features": ["DefaultWorkflowUser", "Communities", &...
0
I've done a simple 3 steps Validation Rule ON/OFF switch - using the Tooling API. We use that while loading data from Prod -> Partial. Maybe it's also useful for someone here .. repo link below.
GitHub: Validation Rule ON/OFF Switch
0
For me, I had a Sales Process (businessProcess) in the force-app directory of a project that is going to be a 2GP and installed in prod, but for our testing sandbox, we deploy the source, not install a package version. The record type was already in the sandbox outside of a package. We've decided to not package the businessProcess in the 2GP, but put it in ...
2
Have you tried using the Salesforce official Diff Feature on the Extension Pack for Salesforce
https://developer.salesforce.com/tools/vscode/en/user-guide/source-diff/
From the terminal, run sfdx plugins:install @salesforce/sfdx-diff.
After the installation is complete, @salesforce/sfdx-diff appears in the list of installed plugins when running sfdx plugins.
...
3
VS Code has an option to detect conflicts on deployment for non-source-tracked orgs. Go to Settings > Salesforce Feature Previews > Salesforcedx-vscode-core: Detect Conflicts At Sync. Note that this is still a limited feature, so some caution is advised.
In the interim, if I want to check for differences, I usually do:
git checkout -b temp-branch
git ...
0
You can deploy the change set. This warning is to indicate that deployment will take time. Once I received same message for a operation which was, as per the message running for 41 mins.
Make sure, you optimize the transactions, so that this warning will not come in next time.
1
I learned that the issue was due to the triggertype 'RecordAfterSave' was only available in Summer 20 and my PROD instance was not an the summer 20 though its sandbox were upgraded earlier.
It has been resolved now by adding a 'release' parameter to my "project-scratch-def.json" file for creating a scratch ORG. Here is the example below.
{
"...
1
The Licence file clearly states:
Force.com Web Service Connector End User License Agreement
Except as described below, Force.com Web Service Connector (WSC) is
Copyright (c) 2005-2013, salesforce.com, inc. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following ...
Top 50 recent answers are included
