DocumentUrlDataResolver: Use UMB_VARIANT_CONTEXT instead of UMB_PROPERTY_DATASET_CONTEXT #19537
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
Pull Request Overview
This PR updates the DocumentUrlsDataResolver to use UMB_VARIANT_CONTEXT instead of UMB_PROPERTY_DATASET_CONTEXT. It updates the import statement, renames the private field, and modifies the context consumption and culture retrieval accordingly.
- Updated import to use UMB_VARIANT_CONTEXT
- Renamed private field from propertyDataSetCulture to variantId
- Adjusted context consumption and culture-based data retrieval
madsrasmussen
added
release/16.1.0
category/dx
iOvergaard
approved these changes
Jun 27, 2025
iOvergaard
deleted the
v16/bugfix/use-variant-context-in-url-data-resolver
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #19507