[TM-950] Allow the collection for linked fields to get stored in the DB form question #239
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
…DB form question.
pachonjcl
approved these changes
May 28, 2024
egrojMonroy
pushed a commit
that referenced
this pull request
Nov 1, 2024
[TM-950] Allow the collection for linked fields to get stored in the DB form question
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.
https://gfw.atlassian.net/browse/TM-950
This fix also included some manual data fixing in prod, but this was the underlying cause. The
collectionfor linked field questions like tree species wasn't getting included in the form question, which meant that it wasn't getting included on the data sent to the server when tree species were edited.