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

fix: metadata definition for ExpressionSetDefinitionVersion #965

Merged
merged 1 commit into from
Dec 18, 2024

Conversation

scolladon
Copy link
Owner

Explain your changes


This is an attempt to fix the metadata definition of ExpressionSetDefinitionVersion

Does this close any currently open issues?


closes #959

Copy link

codeclimate bot commented Dec 17, 2024

Code Climate has analyzed commit 9383c23 and detected 0 issues on this pull request.

View more on Code Climate.

Copy link

codecov bot commented Dec 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (dc57d86) to head (9383c23).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #965   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           40        40           
  Lines         1018      1018           
  Branches       104       104           
=========================================
  Hits          1018      1018           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@scolladon
Copy link
Owner Author

Published under dev-965 npm channel.

$ sfdx plugins:install sfdx-git-delta@dev-965

Hi @PythSomeone !

Here is the PR where the ExpressionSetDefinitionVersion is defined.
Related metadata should still be in the expressionSetVersion folder and end with expressionSetVersion suffix.

IMHO, this metadata kind does not seems to be exposed to the metadata API, only to the tooling API.
But who knows, maybe it will work, let me know the result please!

@PythSomeone
Copy link
Contributor

@scolladon

Both validation and generated delta is correct, no errors were produced and ExpressionSetDefinitionVersion was correctly recognized!

Thanks for quick response :)

@scolladon
Copy link
Owner Author

scolladon commented Dec 18, 2024

@scolladon

Both validation and generated delta is correct, no errors were produced and ExpressionSetDefinitionVersion was correctly recognized!

Thanks for quick response :)

Just to be sure before merging (it is a bit confusing to me) @PythSomeone
the metadata Xml Name (package.xml) is ExpressionSetDefinitionVersion.
Related metadata should still be in the expressionSetVersion folder and end with expressionSetVersion suffix ? right ? (it is this part confusing me)

@PythSomeone
Copy link
Contributor

@scolladon
I understand your concern. The ExpressionSetDefinitionVersion is vital part of Revenue Cloud, I used sfdx to retrieve it from sandbox, the metadata for it was put in that folder with the suffix you mentioned. The naming confuses me too, but I assume this is how it should be.

@scolladon scolladon merged commit c49df86 into main Dec 18, 2024
20 of 22 checks passed
@scolladon scolladon deleted the fix/expression-set-definition-version branch December 18, 2024 10:43
Copy link

Shipped in release v5.51.1.
You can install the new version using the version number or the latest-rc channel

$ sfdx plugins:install sfdx-git-delta@latest-rc
$ sfdx plugins:install [email protected]

Happy incremental deployment!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Expression Set Version and Context Definitions metadata support
2 participants