Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standard Tab Visibility on decomposed Permission Sets not recognized #3163

Open
dschibster opened this issue Jan 3, 2025 · 5 comments
Open
Labels
investigating We're actively investigating this issue validated Version information for this issue has been validated

Comments

@dschibster
Copy link

Summary

When trying to deploy a Permission Set with Standard Tab Visibility turned on (Accounts, Reports, etc.), the files do get recognized after copying them over, however the result of the deployment does not contain the Tab Visibilities. This is using decomposePermissionSetsBeta2, so I know that this is not Safe Haven.

Steps To Reproduce

I do not have a separate repository to reproduce the issue, but I can show you the file structure that is failing to work:

image

Expected result

Tab Visibilities should get picked up by the Permission Set and be deployed, overriden a "Tab Hidden" on the Profile level.

Actual result

The Tab Visibilities for Custom Objects are deployed, but not the ones on the Permission Set Level. Where previously all tabs were visible, no Standard Tab is visible after the deployment.

CLI:
@salesforce/cli/2.71.6 darwin-arm64 node-v22.9.0

Plugin Version:
@oclif/plugin-autocomplete 3.2.14 (core)
@oclif/plugin-commands 4.1.14 (core)
@oclif/plugin-help 6.2.19 (core)
@oclif/plugin-not-found 3.2.31 (core)
@oclif/plugin-plugins 5.4.22 (core)
@oclif/plugin-search 1.2.17 (core)
@oclif/plugin-update 4.6.18 (core)
@oclif/plugin-version 2.2.18 (core)
@oclif/plugin-warn-if-update-available 3.1.28 (core)
@oclif/plugin-which 3.2.21 (core)
@salesforce/cli 2.71.6 (core)
apex 3.6.8 (core)
api 1.3.2 (core)
auth 3.6.82 (core)
data 3.13.5 (core)
deploy-retrieve 3.16.0 (core)
info 3.4.29 (core)
limits 3.3.43 (core)
marketplace 1.3.7 (core)
org 5.2.11 (core)
packaging 2.4.5 (user)
schema 3.3.45 (core)
settings 2.4.9 (core)
signups 2.0.13 (link) /opt/homebrew/lib/node_modules/@salesforce/plugin-signups
sobject 1.4.46 (core)
telemetry 3.6.27 (core)
templates 56.3.34 (core)
trust 3.7.51 (core)
user 3.6.5 (core)
sfdmu 4.33.17 (user)
sfdx-git-delta 5.40.0 (user)
sfdx-hardis 4.52.0 (user)
SF ENV. VARS.
SF_AUTOUPDATE_DISABLE,true
SF_DISABLE_AUTOUPDATE,true
SF_UPDATE_INSTRUCTIONS,Use "npm update --global @salesforce/cli" to update npm-based installations.
Windows: false
Shell: zsh
Channel: stable

Diagnostics

✅ pass - salesforcedx plugin isn’t installed
❌ fail - you have at least one linked plugin
✅ pass - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches apiVersion
✅ pass - [@salesforce/plugin-deploy-retrieve] default target DevHub max apiVersion matches default target org max apiVersion
✅ pass - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches default target org max apiVersion
✅ pass - can access: https://test.salesforce.com
❌ unknown - using latest or latest-rc CLI version
✅ pass - can access: https://appexchange.salesforce.com/services/data
✅ pass - can access: https://developer.salesforce.com/media/salesforce-cli/sf/channels/stable/sf-win32-x64-buildmanifest
❌ fail - [@salesforce/plugin-auth] CLI supports v2 crypto

@dschibster dschibster added the investigating We're actively investigating this issue label Jan 3, 2025
@github-actions github-actions bot added the validated Version information for this issue has been validated label Jan 3, 2025
Copy link

github-actions bot commented Jan 3, 2025

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

@dschibster
Copy link
Author

Currently I can work around it by enabling the Tabs as Visible on Profile Level, but I would rather control this with Permission Sets.

@shetzel
Copy link
Contributor

shetzel commented Jan 4, 2025

@dschibster - is this reproducible when not using the decomposePermissionSetsBeta2 preset?

@dschibster
Copy link
Author

@shetzel No, not quite. The profile before I switched to decomposePermissionSetsBeta2 had all Tabs as Hidden, and only revealed them with the right Permission Sets. That has ceased to work now.

@dschibster
Copy link
Author

@shetzel Additionally, when converting the Permission Sets containing Standard Tab visibility, they also do not get converted. I had to manually create the tabVisibility Files for Standard Tabs in hopes it's a simple conversion error. Didn't throw errors but also didn't do anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigating We're actively investigating this issue validated Version information for this issue has been validated
Projects
None yet
Development

No branches or pull requests

2 participants