Publish reports
Applies To: Dynamics 365 (online), Dynamics 365 (on-premises), Dynamics CRM 2016, Dynamics CRM Online
There are two ways to publish a report for Microsoft Dynamics 365 (online & on-premises):
This topic contains information that applies to both methods.
In This Topic
Privileges for publishing reports
Ownership and sharing for reports
Link a report to another report
Privileges for publishing reports
To publish a report of type Reporting Services Report, you must have the prvPublishRSReport and prvCreateReport privileges for the report entity. However, you do not need the prvPublishRSReport privilege to publish the other two types of reports: Other Report and Linked Report. The report type is specified in the Report.ReportTypeCode attribute.
If the report is associated with the related report categories (ReportCategory), report entity (ReportEntity), and report area (ReportVisibility) entities, you must also have the prvAppendReport and prvAppendToReport privileges for the report entity. By default, the System Administrator and System Customizer security roles have these privileges. For more information, see Security role UI to privilege mapping.
Ownership and sharing for reports
The reports can be organization-owned or user or team-owned. For more information, see Entity ownership. If a report is organization-owned it is visible to the whole organization. If the report is user or team-owned, you can share the report with other users and teams.
You can change the ownership of a report as follows:
Use the IOrganizationService.Update method and set the Report.IsPersonal attribute to a desired value. For organization-owned reports, set the attribute value to false; for user-or team-owned reports, set it to true.
Use the MakeAvailableToOrganizationReportRequest and MakeUnavailableToOrganizationReportRequest messages
Changes in ownership cascade from a parent report to child reports. If you make a parent report organization-owned, all its children reports also become organization-owned. For more information, see Entity relationship behavior.
Link a report to another report
The report can be self-contained or have child reports that provide more detailed information. The parent and the child reports have a parental relationship (see Entity relationship behavior). This means that all operations on the parent record are propagated to the child records (cascade all). However, in a delete operation, the child report is not deleted, but the link between the parent report and the child report is removed.
The child report must contain the information about the parent report ID. To specify the parent report ID, set the Report.ParentReportId attribute in the child report. The linking between the parent report and child report is performed when the child report is created or updated. The parent can have multiple child reports. You must publish a parent report before publishing its child reports. If you create a child report before you create a parent report, you have to update the child report with the parent report ID after the parent report is created.
See Also
Publish a report using the Microsoft Dynamics 365 web service
TechNet: Publish reports
TechNet: Copy reports between Microsoft Dynamics CRM deployments
Developers guide to reports for Microsoft Dynamics 365
Developers guide to reports for Microsoft Dynamics 365
Publish a report using the Microsoft Dynamics 365 web service
Microsoft Dynamics 365
© 2016 Microsoft. All rights reserved. Copyright