Features that aren't implemented in on-premises deployments
This topic lists features that have not been implemented in on-premises deployments of Dynamics 365 for Finance and Operations. The topic is divided into two sections:
- The first section lists features that haven't been implemented yet. These features are not deprecated.
- The second section lists features that are not intended for use with on-premises deployments. There are no plans to implement these features.
Features not yet implemented
The following features have not yet been implemented in on-premises deployments. These features have not been deprecated. If these features are critical to your on-premises deployment, please let us know by providing feedback on the Ideas site.
|Task recorder||Task recorder libraries in Lifecycle Services (LCS) are not supported. Task recordings can be loaded from or saved to the local file system.|
|Support pane||The Support pane (Help & Support > Support) is not yet available.|
|PowerBI.com integration||PowerBI.com integration is not yet available for on-premises deployments. For example, the ability to pin a tile or a report from your PowerBI.com subscription to a workspace is not available.|
|Recurring integrations API||The use of recurring data jobs through the recurring integrations API framework are not supported. You can only use the data management framework package API with on-premises deployments.|
|Microsoft Office integration||SharePoint on-premises support is not yet available. SharePoint online is also not yet supported (due to an authentication issue).
Skype for Business on-premises is not supported.
|Electronic reporting (ER) integration with LCS||The ER integration with LCS is not supported. ER configurations can't be downloaded directly from LCS to Finance and Operations.|
|ER integration with SharePoint||Integration with SharePoint is not supported. SharePoint server can't be configured as a destination for electronic documents generated by using ER.|
|Author Power BI reports using OData||Authoring Power BI reports with OData using Power BI desktop or Excel PowerQuery tools is not supported.|
|Purchase requisitions: Punch-out from external catalogs||It is not possible to check out a shopping cart from an external catalog to a purchase requisition.|
|Trace Parser and PerfTimer||These tools are not working or have limited functionality for this release. These features will be implemented in a future release.|
|SSRS scale out||Currently SQL Server Reporting Services (SSRS) does not support scaling out. This feature will be added in a future release.|
|Telemetry||Currently no telemetry is transferred into the cloud. In a future update we will start transferring telemetry data into the cloud.|
|Data task automation||Data task automation is not currently implemented.|
Features available in 8.1
|Retail||To see a list of currently available retail capabilities in on-premises deployments, see Retail capabilities that are available in on-premises deployments.|
Features not intended for use in on-premises deployments
The following features are not intended for use in on-premises deployments. There are no plans to implement these features in on-premises deployments.
|SSRS Report Viewer control||SQL Server Reporting Services (SSRS) does not support a report viewer control that is compatible with the on-premises web client.
Reports are rendered as PDF documents by the on-premises service. Use extensions to enable embedded drill-thru links in application reports.
|Document Routing Agent||This component is not necessary for on-premises deployments. On-premises deployments are hosted on domain-authenticated servers. This offers secure, direct access to network printer devices.|