Updated create_if and update_if column in entity sheet #307
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.
Updates:
This PR introduces changes to the form logic for creating and updating entities based on a
geopoint
field (new_feature
). The following conditions have been added:create_if
): Entities will be created if thegeopoint
(new_feature
) field has been captured.if(${new_feature}, true(), false())
update_if
): Entities will be updated if the geopoint field has not been captured (i.e., it is empty or missing).if(${new_feature}, false(), true())
Issue:
When new feature geopoint was submitted it should have created new entity but it failed to do so. There was slight error in logic in
create_if
andupdate_if
column:if(${new_feature} = 'yes', true(), false())
like this, since new_feature is geopoint coordinate field comparing it directly to a string ('yes') is not valid, as the field does not return a boolean or string value but rather a set of coordinates.