7
I strongly (but only partially) disagree with the other poster (sorry! :(). I think you should always deploy all of the differences between your repository and org. This is in contrast to deploying only components that have changed in a specific commit. The reason you don't want to deploy just changes in a specific commit is that it doesn't take into ...
1
Error: insufficient access rights on cross-reference id
Usually this error occurs when the Id does not exist in the target org you are deploying to. Look at the Service_Desk_Users group metadata to see if there is a user reference in there. If there is I think Salesforce tries to match up associated user with the email by removing the sandbox affix, so if ...
1
As per Salesforce documentation you can do both in a single deployment.
Adding and Deleting Components in a Single Deployment
You can perform a deployment that specifies components to delete in destructiveChanges.xml and components to add or update in package.xml. The process is the same as with performing a delete-only deployment except that package.xml ...
1
It is better to deploy only the changed components rather than the entire repository. The reasons for this are as below:-
Shorter time for deployment/validation which gives developers more time for fixing the errors.
Errors are thrown only for relevant component, if you deploy entire repository it may happen that components which are on older API can throw ...
1
I think the first important distinction to make when using VSCode, and consequently the underlying SFDX CLI, is if you are doing source driven development, org driven development, or change set driven development.
Have a look at the following Trailhead Trail and a specific module:
Trial - Determine Which Application Lifecycle Management Model Is Right for ...
1
Now with the latest sfdx update(7.21.0) you can run 'sfdx force:source:deploy' command with specific test classes. Check below command.
sfdx force:source:deploy -p "./PathToMetadata" -l RunSpecifiedTests -r TestClass1,TestClass2 -w 33 --verbose --loglevel fatal
https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/...
1
I managed to resolve this error. In my case I was including a PathAssistant in a change set for an unmanaged custom object with no record types. The path was already in Production so it had been successfully moved via change set before.
The problem was the picklist field had different picklist values in Production and the Sandbox. (I added some new options ...
Only top voted, non community-wiki answers of a minimum length are eligible
