Dynamics 365 for Operations Platform Update 6 is released.

April 29th, 2017 by Stephen Jones Leave a reply »

There are 3 locations to get this update from LCS:
1) Binary updates tile – Provides a deployable package that is a combination of latest application and platform binaries. When you apply this package, you will be updated to the latest platform.
2) Platform Update 6 package in Asset library – A deployable package with just the Platform Update 6 binaries.
3) Issue Search – A deployable package with just the Platform Update 6 binaries.

The instructions for upgrading to this platform update are here: https://docs.microsoft.com/en-us/dynamics365/operations/dev-itpro/migration-upgrade/upgrade-latest-platform-update
Key changes:
Browser framework – PowerApps Host control
Dynamics 365 for Operations introduces a new control for developers, the PowerApps Host control. This control allows a developer to host or embed a PowerApp within a Dynamics 365 for Operations form. +

Browser client – Ability to model toolbar actions in the overflow menu
You can now provide a cleaner action story on forms by designating certain buttons in toolbars to always render in overflow. This makes it easier to differentiate actions that users will commonly use versus those that are infrequently or rarely used. To utilize this feature, try the new AlwaysInOverflow metadata property on Button groups inside Toolbars.

Build automation – Automatic update of model version during build
During an automated build, versions of models that are being built are updated to reflect the build number. This allows customers the ability to trace the model versions in the Dynamics 365 for Operations About window back to the build history in Visual Studio Team Services.+

Build automation – Option to include runtime packages in the deployable package of the automated build output
A new option in the build definition instructs the automated build to include any source-controlled runtime packages in the deployable package that is generated for the build output. This allows customers to deploy one package, generated by the automated build, that includes both custom code as well as runtime packages supplied by third parties, such as ISVs.

Number sequence scope extensibility
You can now extend the number sequence scope through extensions.
The scope of a number sequence defines which organization uses the number sequence.
The scope can be combined with fiscal calendar periods to create even more specific number sequences.

• Added the ability to set workspace visibility for different user groups.
• Mobile users will not see pages that they do not have access to in the underlying form in the web client. Before Platform update 6, users could see empty mobile workspaces if they did not have access to any of the pages. Also, the visibility of an entire workspace for a group of users could not be modified.
• New security attributes and APIs are introduced, making it easy to declare visibility of a mobile workspace based on menu items. These APIs can be used to override mobile workspace access for specific user groups.
• Added the ability to auto detect required attributes, through form and table metadata, to denote mobile fields as mandatory during data entry. Action data cannot be submitted to the server if values for the required fields are not provided. (Requirement: Platform update 6 and Mobile April release.)
• Option to fully localize mobile workspaces for all Dynamics 365 for Operations supported languages.

Ideas portal
Dynamics 365 for Operations Ideas forum is now available on Ideas portal.


Comments are closed.