6

I've noticed what I believe to be weird dependency behavior in Microsoft Dynamics CRM 2013. If you have a report with child reports, you cannot delete the child report without deleting the parent report. This seems backwards from any other parent/child relationship in CRM. For example, with parent/child processes, if you want to delete a parent, you have to first delete the children.

Practically speaking, the reason this is an issue is because if you make any significant update to a report, you typically need to delete and re-add the report (because the old one can get cached). The problem is, if you a parent report with multiple child reports, you must effectively delete the parent and all child reports to publish a different version of the child report.

Category:
STATUS DETAILS
Declined