The non-working day calendar with the same name as the working day calendar should not be imported.

Current Situation:

• When importing a non-working day calendar with the same name as a working day calendar that already exists in the inventory, the import API checks for the type of calendar (unique constraint), and as both calendars are of different types, the import API consider them as separated objects and this causes the non working day calendar to be imported successfully.

Steps To Reproduce:

• Create a working day calendar name Cal_1.
• Import a non-working day calendar with the same name Cal_1.
• Try to remove duplicate calendars.

Desired Behavior:

• When importing a non-working day calendar with the same name as a working day calendar that already exists in the inventory, the non-working day calendar should be rejected by the import API.

Workaround:

• Both calendars can be deleted using the GUI if both calendars reside in the same folder.
  • Make sure that all other objects, which should remain, are first moved to a different folder before removing the folder and all of its entries.
  • Click on remove from the context menu of the parent folder holding both calendars.
  • The folder and both calendars were deleted from the database table and from the view without any error.
  • After that recreate the folder and move all other items back to it.