search

scolladon / sfdx-git-delta

Generate the sfdx content in source format from two git commits
Other
413 stars 112 forks source link

[Field Level Security on Orchestration Item ( of vlocity managed package ) does not get promoted for Profiles] #890

Closed shkalantaryCL closed 1 month ago

shkalantaryCL commented 1 month ago

Issue verification check:

What is the problem?

We are using the Jenkins Console Log.txt Scolladon invoked from our Jenkins pipeline. We use SF cli commands to push the changes to our orgs within the same Jenkins pipeline. attached is a console log from promotion of one profile, this does not promoted the FLS on the profile for the Orchestration item, however we have tried below alternate methods and they do promote the same FLS with a profile deployment to the same obj. -Workbench -SF CLi via VS code

What is the parameter and the value you used with it?

What is the expected result?

FLS of the profile on the orchestration item obj gets updated in the target org

What is the actual result?

FLS of the profile on the orchestration item obj does not get updated in the target org and audit trail also does not show any traces of such update

Steps to reproduce

issue has been isolated and a sample log is attached.

Execution context

Operating System: …

yarn version: …

node version: …

git version: …

sfdx version: …

sgd plugin version: …

shkalantaryCL commented 1 month ago

Orch Items Case.docx

scolladon commented 1 month ago

Hi @shkalantaryCL !

Thanks for raising this issue and thanks for contributing in making this project better!

From what I read inside the docx file, there has been made a "dummy" commit to the profile so it is picked up and deployed. What is the content of the commit ? Profile are metadata that are very specific in Salesforce because when a right is removed it is not retrieved with a false value, it is just not retrieved. And also it accept partial deployments, meaning it will change only the content of what is deployed (unlike permission set). It means to deploy a disabled attribution, it needs to be done in the file before deploying the profile as it is not retrievable.

Also, the plugin scope the content of the profile with only what has been changed in the file. This way the deployment is faster and scoped to only what needs to be deployed.

If those explanation does not help you in this situation and you still think there is an issue, please isolate and reproduce the issue in the reproduction playground and share the branch, I'll have a look at it !

scolladon commented 1 month ago

Hi @shkalantaryCL !

I close this investigation because it has been idle for 2 weeks.

Feel free to reopen it with more information, as asked in the previous comment.