Feat/oort 229 update of existing records #8
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
…d test cases for addLayer and editLayer mutation
…d test cases for addLayer and editLayer mutation
…t/AB#54356_enable_filtering_on_geospatial_fields AB#54356 Enable filtering on Geospatial fields
…t/AB#54363_design_model_for_self-service_layers AB#54363 Design Model for self-service layers
…stion type in back end""
…ert-525-revert-506-feat/AB#54321_GIS_start_integration_of_geospatial_question_type_in_back-end Revert 525 revert 506 feat/ab#54321 gis start integration of geospatial question type in back end
…t/AB#58609_created_restendpoint_featurelayers Created rest endpoint for custom feature layers
…t/AB#58618_Move_all_GIS_random_generation_to_the_back_end Feat/ab#58618 move all gis random generation to the back end
…t/AB#58619_extend_layer_model_in_back-end Feat/ab#58619 extend layer model in back end
…t/AB#54365_self_service_endpoints Feat/ab#54365 self service endpoints
…t/AB#58694_add_geojson_generation_in_new_api_endpoint AB#58694 Add GeoJSON generation in new API endpoint
# [2.1.0-beta.1](v2.0.0...v2.1.0-beta.1) (2023-07-03) ### Bug Fixes * code could not compile ([5699e03](5699e03)) * could not get canUpdate / canDelete on meta ([323330a](323330a)) * could not load datasources in layers ([9e1b841](9e1b841)) * editing a dashboard inside a workflow could cause unexpected type issue due to incorrect error handling ([75ccd9a](75ccd9a)) * editRecord could break if previous version did not have any data ([85a2d5c](85a2d5c)) * error on fetching records with no data ([4986e1d](4986e1d)) * geofiltering would break layers if empty ([c22a882](c22a882)) * gis/feature route was broken due to incorrect layout / aggregation setup ([7a3cdd7](7a3cdd7)) * inccorect filter in getautoassigned role ([41a0143](41a0143)) * issue with layers using lat lng fields ([88f75f6](88f75f6)) * layer input could not allow saving of heatmap layer ([6da8988](6da8988)) * prevent any default field to be used in a form ([6e52fda](6e52fda)) ### Features * add dashboard buttons to schema ([fe7bd55](fe7bd55)) * can now group layers ([074cb2b](074cb2b)) * possibility to hide pages' ([f5ca2e6](f5ca2e6)) * query of polygon features on map ([fc33c06](fc33c06))
…t/AB#68305_Update_backend_code_to_support_EMS2_pulljob Feat/AB#68305 update backend code to support ems2 pulljob
…/search-grid-calculated-field-in-resource fix/search-grid-calculated-field-in-resource
…zone * started cast am and pm hour to iso format * fixed issue of timezone * fixed info * lint fixed
…/AB#68727_pulljobs-failing fix: pulljobs failing would crash server
…ents * fixed graphql endpoint not accept empty after edited * removed console logs * improve API configuration edit mutation --------- Co-authored-by: Antoine Hurard <antoine.reliefapps@gmail.com>
Co-authored-by: Antoine Hurard <antoine.reliefapps@gmail.com>
* fix: creates files folder if it doesn't exist * generalize logic for folder creation * add more explanation to the downloadFile method --------- Co-authored-by: Antoine Hurard <antoine.reliefapps@gmail.com>
* Unit test cases failed to resolve issue * Unit test cases failed to resolve issue * Unit test cases failed to resolve issue
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
On exporting records, the incremental id of each record is exported as well
On importing records, if an incremental id is provided (a valid one), the record with that id will be update instead of adding a new copy of the record
Closes the old PR
Ticket
OORT-229: Being able to upload update of existing records
PR on ems-backend
Type of change
How Has This Been Tested?
Export the record from a form/record. Notice that a column with the name IncrementalID should appear, followed by the incremental ID of each of the exported records
When uploading records, if a valid id is provided that record will be updated, if not (not provided or invalid) a new record will be added
Screenshots
Checklist:
( * == Mandatory )