The MusicMaster/Dalet link is reliant upon the MusicMaster DaletID field and the Dalet ItemCode field acting as the "common key" between the two systems. Dalet will create new entries in MusicMaster when an item is linked to the MuisicMaster directory. As long as an item is linked via this folder any updates to the Dalet asset manager will push data updates to the related MusicMaster entry. However, there are a few scenarios in which these two items can become disambiguated. These scenarios and the resulting consequences are detailed below.

• If you delete a song link out of the Dalet MusicMaster (or MusicMaster2) folder: The song will be removed from the parent and children databases, all play history will be permanently removed.
• If you delete a Dalet linked song out of the parent database: the song will remain in Dalet, the next time that songs metadata is updated in Dalet it will create a new entry in the parent (but not linked to the children, with all play history etc. gone).
• If you delete the DaletID out of the parent: scheduling from MusicMaster will not work properly, reconciling to MusicMaster will not work properly. If the blanked song is scheduled it will result in an empty audio item being created in Dalet.
• If you delete a linked song out of Dalet: its link will also be deleted, removing the song from 3rd service and children databases.
• If you change the item code of a linked item in Dalet: The two items will be disambiguated, any changes in Dalet will not be reflected in MusicMaster. Scheduling the piece form MM will result in a blank audio item being created, playlist reconciliation of the piece will not work properly.