Don't serialize the generated attachment URL on export. #6921
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
cnathe
approved these changes
Aug 12, 2025
Contributor
cnathe
left a comment
cnathe
left a comment
There was a problem hiding this comment.
Code review complete and issue verified in feature branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Rationale
related issue
The list attachment field download URL contains token replacement of the field name that can cause list import issues. There isn't really a need to serialize this to the list archive unless a user has explicitly set it on the
PropertyDescriptor. The code change needs to unset the value since the base classwriteColumndoesn't make this distinction.Related Pull Requests
LabKey/testAutomation#2624