-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSV customised location sample file #1531
Comments
…ction for Locations Upload / Sample download
…eb/locationHierarchies response
…rchy input params during locations sample file download
…mple file download
pls check this |
@AchalaBelokar you would get only those location types, that are part of the selected locationHierarchy. |
@AchalaBelokar uuid for location edit not needed, since location names are going to be unique. Just adding here for later reference, since I also keep forgetting the reasons. |
Issue:
https://avni.freshdesk.com/a/tickets/3603
https://avni.freshdesk.com/a/tickets/2478
Acceptance criteria:
- Have the first option selected by default in both mode and location hierarchy. Should not be able to unselect it by clicking again. Thats how it already works for mode.
- Display location hierarchies only for create mode and not for other modes
The sample file should be according to the location hierarchy and mode selected
sample file for create
- Location hierarchy should be there based on highest to lowest level
- Placeholder values need to be present as mentioned
- Ignore last 4 columns mentioned - Out of scope
sample file for Editing location
- Modify the headers as mentioned in the sample file
- Have the placeholder fields(3rd row) and descriptor row(2nd row) like mentioned
- Ignore last 4 columns mentioned - Out of scope
Link this here
Ignore the below:
Suggestions:
In Edit+create we are allowing to create the lowest location as well - make it to be created only via Create mode.
Since we are allowing to update parent - mention the entire hierarchy along with uuid to update to keep the expectation uniform
In the locations export, along with titleLineage - mention it in separate columns as well
When data uploaded with that
*
it needs to continue to work.Current behavior that need not be handled:
Note:
Inputs:
Questions:
Analysis notes:
https://avni.freshdesk.com/a/tickets/2700 - degree in GPS and location already existing
--- degree - solved by data in sample file
--- location already existing - it does error out - so donno whats the case
https://avni.freshdesk.com/a/tickets/2442 - location properties related - possible answers are add, date add - add columns
--- should be fine since configuration is handled by implementation team
The text was updated successfully, but these errors were encountered: