The Dynamics 365 for Finance and Operations platform update 8 has been released on June 28, 2017.
We’re excited to bring you another monthly release that combines new features and a number of quality improvements. This topic describes features that are either new or changed in Dynamics 365 for Finance and Operations, Enterprise edition platform update 8. As part of this update the platform has also been renamed to Dynamics 365 Unified Operations.
Go to the Dynamics 365 Roadmap to find supplemental information about new features and learn more about what new features are in development. For information about the bug fixes included in Platform update 8, log in to Lifecycle Services (LCS) and view this KB article.
Introducing Dynamics 365 for Finance and Operations, Enterprise edition
Users and developers will see an updated product name ("Microsoft Dynamics 365 for Finance and Operations, Enterprise edition") and product icon in the web client. Some platform components (for example, the developer tools and the mobile application) that are shared by Dynamics 365 for Finance and Operations, Dynamics 365 for Retail, and Dynamics 365 for Talent will now appear as "Dynamics 365 Unified Operations".
Development and customization - Changing the extended data type (EDT) on a table field using table extensions
Using table extensions, a developer can change the Extended Data Type (EDT) property of a table field. Developers can only select EDTs that are derived from the current one. For more information, see Customize with extensions and overlayering.
Development and customization - Compliance properties on table fields
A new property named General Data Protection Regulation (GDPR) is now available on table fields for the developer to set. It is used to classify the data field for compliance with GDPR.
Available options are:
- Access control data - Data used to manage and access to administrative roles or sensitive functions.
- Customer content - Content directly provided/created by admins and users. This is the default value.
- End User Identifiable Information (EUII) - Data that identifies or could be used to identify the user of a Microsoft service. EUII does not contain Customer content.
- End User Pseudonymous Information (EUPI) - An identifier created by Microsoft tied to the user of a Microsoft service. When EUPI is combined with other information, such as a mapping table, it identifies the end user. EUPI does not contain information uploaded or created by the customer (Customer content or EUII).
- Support data - Data provided to Microsoft as part of Support activities.
- Account data - Customer billing information and payment instrument information. Administrator contact information, such as tenant administrator’s name, address, or phone number.
- Public personal data - Publicly available information that Microsoft obtains from external sources. Public personal data is not Customer content, EUII, or EUPI since the data was not input by the customer.
- Organization Identifiable Information (OII) - Data that can be used to identify a tenant, generally config or usage data. This data is not linkable to a user and does not contain Customer content.
- System metadata - Data generated while running the service, not linkable to a user or tenant.
- Public non-personal data - Publicly available information that Microsoft obtains from external sources. Does not contain Public personal data.
Improved viewing experience for Application reports
There is a new and improved viewing experience for customers when interacting with Analytical and Operational reports in Dynamics 365 for Finance and Operations, Enterprise edition. This change offers a streamlined toolbar and clear preview of the document that is produced when rendered as a PDF file or sent directly to the printer. To date, customers have rendered over 1.1 million document reports powered by SQL Server Reporting Services (SSRS). In addition, the Dynamics 365 for Finance and Operations, Enterprise edition July 2017 update includes 20+ analytical reports authored using Power BI Desktop. This feature offers a significantly enhanced viewing experience while interacting with both document and analytical style application reports. Customer benefits:
- Reliability - Customers will now be presented with a view that is consistent with the output when documents are sent directly to the printer. Based on direct feedback, the most common use case for viewing a report on screen is to preview the output that will be shared with others, most often by email. Customs can now rely on a screen rendition that more closely matches the document produced by SSRS.
- Simplicity - Customers can fully engage with application reports using mobile devices with relatively small screens. On these devices, every inch of the screen is important. By removing the page caption, users have more screen space with which to view and interact with application reports.
Table browser is now in read-only mode
The table browser form is now in read-only mode on runtime environments (Sandbox Tier-2+ and Production).
The table browser form is designed for developers to quickly create and edit test data on development environments. It was also available to system administrators on runtime environments. As of Platform update 8, system administrators can only access the table browser in read-only mode on runtime environments, this is in reaction to live incidents caused by human error when system administrators inadvertently edited or removed live system data.
Deployment option (on-premises)
Some organizations are not ready to store their company’s mission critical data in the cloud. This requirement, in many cases, is due to industry regulations, country or geographic cloud adoption, recent data center investments, or an organization’s enterprise standards. For these customers, we are excited to announce a new deployment option that will not require business data to be stored in the cloud. This deployment option supports running your business processes on-premises, supporting local transactions and storage of local business data, without replication of your business data to the Microsoft cloud. In these cases, the typical replication of business data in the Microsoft cloud (referenced in the cloud and edge scenario) is simply switched off.
Cloud synchronization of data enables Microsoft to embed intelligence into business processes – embedded analytics, machine learning, and a vast range of capabilities are best served from the Microsoft cloud. With this option, customers now have a choice – an option to turn on or turn off cloud synchronization of their business data. If customers turn off cloud synchronization, no business data leaves their trustee’s boundaries. Also, functions like embedded Power BI, Aggregated Views, and Azure Machine Learning services-based efficiencies are not available when cloud data synchronization is turned off. Customers can choose to take advantage of the embedded intelligence functions by simply turning on data synchronization to the cloud.
An environment with both on-premises business data and cloud data synchronization is referred to as a Cloud + Edge deployment option. Refer to the table for a closer comparison of differences between these options.
Our cloud-based Application Lifecycle Management (ALM) functions, including diagnostics, monitoring, usage telemetry, and production updates, are provided through Microsoft Dynamics Lifecycle Services (LCS). LCS is required for efficient upkeep and operation of your Dynamics 365 for Finance and Operations solutions in all deployment options. After nearly a year of operating the cloud service, we have seen that LCS-based management leads to more predictable deployments and provides customers with a better support and service experience. All deployment options for Finance and Operations require LCS for their operation.
For the on-premises deployment scenario, the application servers and SQL database will run in a customer’s or partner’s data center. Customers and partners manage the application lifecycle through LCS in the Microsoft cloud, including designing the business processes, creating and deploying the software image to deploy onto the on-premises nodes, monitoring the on-premises nodes in a system health dashboard, and keeping up with innovation from Microsoft.
For more information, see The right cloud option for your business. This blog post refers to the “local business data” deployment capability. This is the capability that’s called “on-premises” in the product and documentation.