-
Notifications
You must be signed in to change notification settings - Fork 43
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
Should be able to delete location type when no locations of that type exist #1290
Comments
…so name can be reused
Fixed 2nd issue by renaming address level type on deletion so same name can be used again for a new address level type. Unable to simulate the 1st issue - was able to delete child type when it did not have any children or levels of that type. The error message in the screenshot is not the latest so perhaps there was incorrect version of server deployed while testing. |
|
…dress level types so names can be reused
…dress level types so names can be reused (cherry picked from commit 26e5fda)
@1t5j0y good to mention last_modified_by_id(using superadmin of yours) also I think, Previously when something via migrations have gone wrong it was with this, able to find a pattern and identified the root cause. Let me know if you think otherwise. |
good to have but not necessary for this particular one in my opinion since we are only touching already voided entities. Also, migrations should use last_modified_by_id 1 to differentiate migrations from manual fixes. Maybe we need |
yeah agreed |
QA References : |
As is:
Currently when a location type once created in App designer cant be deleted
Need:
For someone who is new, when they have set the hierarchy incorrectly when newly trying to setup, it becomes irreversible for them and leads to confusion
AC:
The text was updated successfully, but these errors were encountered: