Skip to content
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 upload issues of previous release #1347

Closed
Tracked by #1672
mahalakshme opened this issue Sep 23, 2024 · 4 comments
Closed
Tracked by #1672

CSV upload issues of previous release #1347

mahalakshme opened this issue Sep 23, 2024 · 4 comments
Assignees

Comments

@mahalakshme
Copy link
Contributor

mahalakshme commented Sep 23, 2024

Issue:

As part of a previous card, an extra condition was additionally implemented with respect to updating the parent of a location to be that of the same type as that of the previous one.

Analysis:

Especially in organisations with multiple hierarchies, during upload, it is possible to incorrectly upload, and they might want to correct it.

AC:

  • On Edit of location, type of the new location can be different from that of the previous one. So the above check can be removed.
  • And instead add this check: The new location, should be of type, of the immediate parent as configured in the location type. If not then show an error message. Eg: lets say Ahmednagar is the child location name mentioned as part of full hierarchy then the error message need to be "Only parents of location type 'A' is allowed for Ahmednagar."

Issue:

  • The descriptor row is not the second row in the Edit Location sample file creating confusion regarding what can be retained and what needs to be removed.
  • Same in create location sample file - Message indicating "Mandatory to mention the parent locations to which the location to be created belongs to" is in the placeholder row.

AC:

Refer the sample files in this card to know the order and the content - for create and Edit location sample files.

Issue:

In the upload status, read considers descriptor row also as one row, but like header row that needs to be ignored.

I uploaded only one row both times.
Image

AC:

  • In the rows read and completed - dont count the descriptor row
  • applies for Locations create, edit, and Users and catchments upload.
@mahalakshme mahalakshme converted this from a draft issue Sep 23, 2024
@mahalakshme mahalakshme changed the title During CSV upload support new parent can be of different type than the existing parent During location CSV update support new parent can be of different type than the existing parent Oct 3, 2024
@mahalakshme mahalakshme changed the title During location CSV update support new parent can be of different type than the existing parent During location CSV update/edit, support new parent can be of different type than the existing parent Oct 3, 2024
@mahalakshme mahalakshme changed the title During location CSV update/edit, support new parent can be of different type than the existing parent CSV upload issues of previous release Oct 3, 2024
@mahalakshme mahalakshme moved this from In Analysis to Ready in Avni Product Oct 3, 2024
@himeshr himeshr self-assigned this Oct 4, 2024
@mahalakshme
Copy link
Contributor Author

@himeshr you are right. I got confused with the case in Hasirudala Karnataka - Two children types can have same parent type, but a child type can have only one parent type. So this: "Only parents of location types A and B are allowed for Ahmednagar." is not valid.

@himeshr
Copy link
Contributor

himeshr commented Oct 7, 2024

himeshr added a commit to avniproject/avni-server that referenced this issue Oct 7, 2024
himeshr added a commit to avniproject/avni-server that referenced this issue Oct 7, 2024
himeshr added a commit to avniproject/avni-server that referenced this issue Oct 7, 2024
himeshr added a commit to avniproject/avni-server that referenced this issue Oct 7, 2024
himeshr added a commit to avniproject/avni-server that referenced this issue Oct 7, 2024
himeshr added a commit to avniproject/avni-server that referenced this issue Oct 7, 2024
@himeshr
Copy link
Contributor

himeshr commented Oct 7, 2024

We have to spend considerable effort to optimize bulk upload of data, as currently the chunk size is set to 1 to perform proper error handling at every row level, which results in repeated invocation of common actions that should ideally be performed only once for each file upload or at the least once for a large chunk of the uploaded content.

@himeshr himeshr moved this from In Progress to Code Review Ready in Avni Product Oct 7, 2024
@1t5j0y 1t5j0y moved this from In Code Review to QA Ready in Avni Product Oct 8, 2024
@AchalaBelokar AchalaBelokar moved this from In QA to Done in Avni Product Nov 12, 2024
@1t5j0y
Copy link
Contributor

1t5j0y commented Nov 20, 2024

AC for issue 1 not satisfied.
Prod org inslocation.
errors-sample-locations(4)(1).csv

@1t5j0y 1t5j0y reopened this Nov 20, 2024
@github-project-automation github-project-automation bot moved this from Done to Triaged in Avni Product Nov 20, 2024
@1t5j0y 1t5j0y moved this from Triaged to QA Failed in Avni Product Nov 20, 2024
@1t5j0y 1t5j0y self-assigned this Nov 20, 2024
1t5j0y added a commit to avniproject/avni-server that referenced this issue Nov 21, 2024
@mahalakshme mahalakshme moved this from In Code Review to QA Ready in Avni Product Nov 21, 2024
@AchalaBelokar AchalaBelokar moved this from In QA to Done in Avni Product Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

4 participants