COMCL-754: Fix Custom Field Values For Cases #1040
Merged
Conversation
This file contains 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
erawat
requested changes
Aug 28, 2024
shahrukh-compuco
force-pushed
the
comcl-754-fix-case-custom-fields
branch
from
ad6ee00 to
d1cc8fe
Compare
erawat
approved these changes
Aug 29, 2024
erawat
approved these changes
Aug 29, 2024
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.
Overview
This pr fixes a bug due to which the value of a custom field for a case was not displayed correctly.
Before
The value of custom field was getting replaced with contact names.
After
The actual value of a custom field is displayed.
