You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is the current repository fully deployable at the commit SHA provided with the 'from' parameter of the command?
What is the problem?
We have observed that the deployment on packages with only changes to territory do not get along to Salesforce , even though the build status is successful in Jenkins but the request is not sent to SF. However , if we have changes to other components in addition to the territories in the same build , then only the build reflects on SF UI. But even in the second scenario the changes to territory component do not get deployed/ reflected on the target org.
What is the parameter and the value you used with it?
Thanks for raising this issue, thanks for your interest in the plugin and for your help to improve it.
Per the description of this issue, the plugin seems to do its job fine (generating xml files and delta files).
I found one fixed issue related to what you described in the sfdx-cli
I have couple questions:
What is the command and the parameters you use to deploy territory metadata?
Do you have this issue using this command even from the whole sources of you repository? (without using incremental generation with the plugin)
@shkalantaryCL closing this issue as it may be related to a solved known issue and it has been open for a very long time
Feel free to reopen it with more information
Issue verification check:
What is the problem?
We have observed that the deployment on packages with only changes to territory do not get along to Salesforce , even though the build status is successful in Jenkins but the request is not sent to SF. However , if we have changes to other components in addition to the territories in the same build , then only the build reflects on SF UI. But even in the second scenario the changes to territory component do not get deployed/ reflected on the target org.
What is the parameter and the value you used with it?
mkdir sfdx-delta
sudo sfdx sgd:source:delta --to 'commit id' --from 'previous commit id' --output sfdx-delta --generate-delta
What is the expected result?
sample of a delta package containing both territory & other changes :
Account-PMGS-WLS-IC-Advisor Accounts Account-WLS-IC-Advisor Accounts Layout Advanced_Advisor_Practices.territory2 Territory2Model 53.0What is the actual result?
actual and expected delta package generated on the Jenkins output log are same & look good.
Steps to reproduce
Operating System: Windows 10
yarn version: …
node version: …
git version: 2.24.4
sfdx version: 7.108.0
sgd plugin version: …
The text was updated successfully, but these errors were encountered: