cmp_discovery_ldc_config records are created for some accounts even though all accounts under "Discover all related accounts listed below" slush bucket are removedDescriptionWhen creating a Cloud Discovery schedule you can select which accounts you would like to discover.When we move accounts which have the same exact name " from "Selected" window to "Available" window of the slush bucket only one of those accounts actually becomes "unselected".The UI shows that all the accounts are moved to "Available" though. This causes the issue of that only 1 account (with the same name) will not be present in cmp_discovery_ldc_config and the remaining ones will still be discovered and be present in cmp_discovery_ldc_config for the created schedule. Cause: The $scope object has *uniqueIdentifier* returned as undefined, due to which it picks it up as label.$scope.uniqueIdentifier = $scope.uniqueIdentifier ? $scope.uniqueIdentifier: $scope.label;Because of this issue, when we try to move accounts with "Same Name" from "Right" Part to "Left" part of Slush bucket only one of those accounts actually becomes "unselected" although in UI it shows all the accounts are moved.So if there are multiple accounts with same name only one of the account with same name gets removed from slush bucket and for rest of them will still get discovered.Steps to Reproduce 1. Please go to https://<instance>.service-now.com/discovery_schedule_list.do2. Click the button Cloud Discovery at the top3. In the first screen please select cloud provider4. Fill in name5. For MID Selection Method please go with the first method (auto select)6. Select "Select Option" from options6. Then wait for the list of accounts to load to select an account7. Then UNCHECK the option "Discover all related accounts listed below". Make sure that you remove all accounts from the "selected" slush bucket to the left window.8. Move to the next screen9. Then UNCHECK the option "Discover all datacenters listed below."10. Select 1 or 2 regions as discovered LDC.11. Move to the next screen12. Then UNCHECK the option "Discover VMs by IP address (Recommended)"13. Move to the next screen14. Select Frequency as "Once"15. Select a start date (can be any but preferably in the near future)16. Then update the cancel discovery timer to just an hour17. Then IMPORTANT: do not click Finish and Run but instead just click Finish to not run the actual schedule18. Wait for the schedule to create, navigate to it, open it, look at the related list called "Discovery Config - Logical Datacenters" to see some accounts are still included here.WorkaroundNo workaround is availableRelated Problem: PRB1657982