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
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.
Description
Forms couldn’t tell whether they were being opened to create a new record or update an existing one, which made it hard to build the email-chain style behavior where field values need to flip on each edit. This change adds a small SurveyJS helper, isUpdate(), that checks whether the current survey has an existing record attached, so builders can use it directly in expressions to reset or swap values during updates without adding new form state. I also added a focused unit test for both create and edit modes.
Possible expression for isUpdate():
iif(isUpdate(), 'Updated value', 'Initial value')Useful links
Type of change
Checklist:
( * == Mandatory )