Creating organisation with same name not handled

[AchalaBelokar]

Need:

So far 3 times, this issue has been raised by different people. To make our work process smooth.

Describe the bug
Not able to create organisation through super admin on staging
Login with admin and try to create a organisation
it is showing communication error

To Reproduce
Steps to reproduce the behavior:

1. Login with admin user
2. Click on organisation
3. try to create a organisation with the same name as already existing organisation.
4. See error

Screen.Recording.2024-07-23.at.2.36.50.PM.mov

Expected behaviour

• Show error message under the Name field stating 'Organisation with the same name already exists. Please try with a different name.'
• The below common message 'The form is not valid. Please check for errors.' also need to show.

• The above issue happens for same dbname, schemaname, etc as well - Handle them like the above.
• Handle other additional validations applicable to db_user also - comment on the same.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Developer Checklist(Developer fixing the bug should fill this checklist)

• Does the fix require extensive regression testing?
  • Yes
  • No
• Are you mentioning the required scenarios that could be affected?
  • Yes
  • No

[1t5j0y]

@AchalaBelokar please try with another org name. There is already an org with the name 'testbun'

[mahalakshme]

since it should 've shown a readable error message ll schedule it in a different release

[vedfordev]

Tried with CustomToolbar and {handleSubmitWithRedirect,handleSubmit,save} still not working. Seems like older version not support this.

[1t5j0y]

@vedfordev please share the commit(s) for this issue. Couldn't locate them

[vedfordev]

@vedfordev please share the commit(s) for this issue. Couldn't locate them

@dinesh2096 by mistake moved to review. it is in progress.

[mahalakshme]

@vedfordev please find my comment above

[vedfordev]

@vedfordev please find my comment above

@dinesh2096 added constraint and notification.

[vedfordev]

@mahalakshme server migration causing issue due to there are many org with usernamesuffix blank and duplicates.

SELECT username_suffix,count(id)
FROM public.organisation
group by username_suffix
having count(id) > 1
;
-- 24 with null

SELECT schema_name,count(id)
FROM public.organisation
group by schema_name
having count(id) > 1
;


select *
from organisation
where username_suffix is null
;

[mahalakshme]

@vedfordev I will move this back to 'In Analysis'. Will get back on this.

[mahalakshme]

@vedfordev we need not add unique constraint for username suffix

[vedfordev]

@vedfordev we need not add unique constraint for username suffix

@dinesh2096 please check this and UI Changes are on branch 10.2

@mahalakshme I reverted the migration change in master Link