New button is enabled in child applet if parent applet does not have records

our end users have concerns having new button enabled in child applet if there are no records in the parent. Even though it throws error saying 'you don't have necessary permissions' it is not intuitive for user keeping the button enabled. This behavior is across the application. The button in the child applets should be enabled only if the parent record is committed. Anyone aware of this as a product defect ? or this is the expected behavior ?  if expected behavior, what scenario will justify of keeping that enabled? this is in IP15 FINS OUI