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

Deploying changes to ContextDefinition does not update ContextDefinitionVersion #3105

Closed
robertwheelerprodly opened this issue Nov 11, 2024 · 10 comments
Labels
owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team.

Comments

@robertwheelerprodly
Copy link

robertwheelerprodly commented Nov 11, 2024

Expected result

Trying to deploy changes for a ContextDefinition type mainly the ContextDefintionVersion portion.

Actual result

Deploying to a sandbox it shows that the file has successfully been deployed with a status of changed. When pulling the file from the sandbox the result shows changed and when opening the file it still shows the original version as if the deployment was not successful. If the change is to the ContextDefinition then it will update, but if a change to the ContextDefinitionVersion is not changed.

Additional information

Screenshot 2024-11-11 at 5 15 15 PM
Screenshot 2024-11-11 at 5 16 10 PM
Screenshot 2024-11-11 at 5 25 19 PM

System Information

CLI:
@salesforce/cli/2.65.8 darwin-x64 node-v20.17.0

Plugin Version:
@oclif/plugin-autocomplete 3.2.7 (core)
@oclif/plugin-commands 4.1.5 (core)
@oclif/plugin-help 6.2.16 (core)
@oclif/plugin-not-found 3.2.24 (core)
@oclif/plugin-plugins 5.4.15 (core)
@oclif/plugin-search 1.2.13 (core)
@oclif/plugin-update 4.6.8 (core)
@oclif/plugin-version 2.2.15 (core)
@oclif/plugin-warn-if-update-available 3.1.20 (core)
@oclif/plugin-which 3.2.16 (core)
@salesforce/cli 2.65.8 (core)
apex 3.5.5 (core)
api 1.3.1 (core)
auth 3.6.70 (core)
data 3.9.0 (core)
deploy-retrieve 3.15.4 (core)
env 3.0.33 (user)
functions 1.23.0 (user)
info 3.4.15 (core)
limits 3.3.37 (core)
marketplace 1.3.2 (core)
org 5.0.2 (core)
packaging 2.8.12 (core)
schema 3.3.39 (core)
settings 2.4.2 (core)
signups 2.5.23 (user)
sobject 1.4.44 (core)
telemetry 3.6.18 (core)
templates 56.3.26 (core)
trust 3.7.38 (core)
user 3.6.0 (core)
sfdx-plugin-source-read 1.3.0 (user)
SF ENV. VARS.
SF_BINPATH,/Users/rwheeler/.local/share/sf/client/bin/sf
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
✅ pass - you don't have any linked plugins
❌ unknown - using latest or latest-rc CLI version
✅ pass - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches apiVersion
✅ pass - can access: https://test.salesforce.com
✅ 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

@robertwheelerprodly robertwheelerprodly changed the title Deploying new ContextDefinition does not update version Deploying changes to ContextDefinition does not update version Nov 11, 2024
@robertwheelerprodly robertwheelerprodly changed the title Deploying changes to ContextDefinition does not update version Deploying changes to ContextDefinition does not ContextDefinitionVersion Nov 13, 2024
@robertwheelerprodly robertwheelerprodly changed the title Deploying changes to ContextDefinition does not ContextDefinitionVersion Deploying changes to ContextDefinition does not update ContextDefinitionVersion Nov 13, 2024
@robertwheelerprodly
Copy link
Author

Is there anything else I need to add here, this is a problem for me since trying to deploy a newer version of the ContextDefinitionVersion

@WillieRuemmele
Copy link
Member

hi @robertwheelerprodly - could you provide some steps to create the ContextDefinition + CDV, and any perms, settings, that are required to create an org with it?

@robertwheelerprodly
Copy link
Author

robertwheelerprodly commented Nov 13, 2024 via email

@robertwheelerprodly
Copy link
Author

robertwheelerprodly commented Nov 19, 2024 via email

@robertwheelerprodly
Copy link
Author

robertwheelerprodly commented Nov 20, 2024 via email

@WillieRuemmele
Copy link
Member

we'll try to get an org setup with this license, but it may take some time

@robertwheelerprodly
Copy link
Author

robertwheelerprodly commented Nov 25, 2024 via email

@shetzel shetzel added the owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team. label Dec 2, 2024
Copy link

github-actions bot commented Dec 2, 2024

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.

@shetzel
Copy link
Contributor

shetzel commented Dec 2, 2024

Hi @robertwheelerprodly - the quickest way to a solution for this problem is to open a support case. This is a server side problem versus a CLI issue. Tell the Support rep that the owning server side team is called, "CS - Harmony" in the Context Service cloud. They will open an investigation for that team to triage and fix.

@shetzel shetzel closed this as completed Dec 2, 2024
@robertwheelerprodly
Copy link
Author

robertwheelerprodly commented Dec 3, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
owned by another team The Salesforce CLI team does not own this work but will pass on the information to the correct team.
Projects
None yet
Development

No branches or pull requests

3 participants