You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
there are cases when you are using some zone elsewhere in the system as a relationship and when you try to delete the base zone, admin-api generates something like this The selected Zone cannot be deleted as it is used in the following TaxRates but the end user cannot see any message. that message is what shown inside browser's network inspect. in this scenario shop manager don't know what to do because there is no feedback to say removal failed, you should first remove the dependent data. also note that this is not only for zone entity, i saw this behavior in some other relational entities as well.
Describe the solution you'd like
if we could show the end user of admin-ui that something went wrong and help them fix the issue they can fix themselves would be really nice.
Describe alternatives you've considered
any kind of improvement on messaging system and alerts would be nice, specifically on foreign key checks / entity relationship which prevents data removal due to a known/logical reason.
Additional context
currently there is no additional context required to describe the improvement.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
there are cases when you are using some zone elsewhere in the system as a relationship and when you try to delete the base zone,
admin-api
generates something like thisThe selected Zone cannot be deleted as it is used in the following TaxRates
but the end user cannot see any message. that message is what shown inside browser's network inspect. in this scenario shop manager don't know what to do because there is no feedback to sayremoval failed, you should first remove the dependent data
. also note that this is not only forzone
entity, i saw this behavior in some other relational entities as well.Describe the solution you'd like
if we could show the end user of
admin-ui
that something went wrong and help them fix the issue they can fix themselves would be really nice.Describe alternatives you've considered
any kind of improvement on messaging system and alerts would be nice, specifically on
foreign key checks
/entity relationship
which prevents data removal due to a known/logical reason.Additional context
currently there is no additional context required to describe the improvement.
The text was updated successfully, but these errors were encountered: