re-start the SQL reporting services
Friday, 21 April 2017
Tuesday, 18 April 2017
Recent versions of Dynamics 365 for Operations
| Release | Version | Build number | Availability | Support end date | To learn more |
|---|---|---|---|---|---|
| Microsoft Dynamics 365 for Operations platform | Platform update 5 | 7.0.4475.16165 | March 2017 | March 31, 2018 | |
| Microsoft Dynamics 365 for Operations platform | Platform update 4 | 7.0.4425.16161 | February 2017 | February 28, 2018 | |
| Microsoft Dynamics 365 for Operations | 1611 | 7.1.1541.3036 | November 2016 | November 30, 2019 | What’s new or changed in Dynamics 365 for Operations version 1611 (November 2016) |
| Microsoft Dynamics 365 for Operations platform | Platform update 3 | 7.0.4307.16141 | November 2016 | November 30, 2017 | What’s new or changed in Dynamics 365 for Operations platform update 3 (November 2016) |
| Microsoft Dynamics AX platform | Platform update 2 | 7.0.4230.16130 | August 2016 | August 31, 2017 | What’s new or changed in Dynamics AX platform update 2 (August 2016) |
| Microsoft Dynamics AX platform | Platform update 1 | 7.0.4127.16103 | May 2016 | May 31, 2017 | What’s new or changed in Dynamics AX platform update 1 (May 2016) |
| Microsoft Dynamics AX application | 7.0.1 | 7.0.1265.23014 | May 2016 | June 30, 2017 | What’s new or changed in Dynamics AX application version 7.0.1 (May 2016) |
| Microsoft Dynamics AX platform | 7.0 | 7.0.4030.16079 | February 2016 | January 31, 2017 | What’s new or changed in Dynamics AX 7.0 (February 2016) |
| Microsoft Dynamics AX application | 7.0 | 7.0.1265.3015 | February 2016 | June 30, 2017 | What’s new or changed in Dynamics AX 7.0 (February 2016) |
Support matrix
The following table provides information about the multiple releases of Microsoft Dynamics 365 for Operations platform and Dynamics 365 for Operations application, and which versions are supported.
| Microsoft Dynamics AX 7.0 | Microsoft Dynamics AX application 7.0.1 | Microsoft Dynamics 365 for Operations (1611) | |
|---|---|---|---|
| Platform update 5 | Compatible | Compatible | Compatible |
| Platform update 4 | Compatible | Compatible | Compatible |
| Platform update 3 | Compatible | Compatible | Compatible |
| Platform update 2 | Compatible | Compatible | |
| Platform update 1 | Compatible | Compatible | |
| Platform 7.0 | Compatible |
Update policy
Microsoft Dynamics 365 for Operations is serviced as a cloud offering. Updates to the Dynamics 365 for Operations platform and application will be handled in the following manner:
- Dynamics 365 for Operations cloud platform updates will be initiated by Microsoft. After you provide your consent, platform updates will be rolled out to provide critical updates and features to the Dynamics 365 for Operations cloud platform.
- Dynamics 365 for Operations application updates will be initiated by you, the customer. After you provide your consent, application updates will be applied to your production environment.
Application and platform updates will be scheduled with you, the customer. When platform and application updates are released, a sandbox environment will be made available to you, so that you can validate the updates. For details about how the sandbox environment will be provided, see the licensing guide.
Important: Some updates may be mandatory and require no consent. To help protect our customers and the service, Microsoft may apply critical updates directly to your Dynamics 365 for Operations production environment. If a critical issue is discovered, the following events will occur:
- Microsoft will notify you about the critical update.
- Microsoft will notify you of the required downtime window (if any) and apply the critical update to your Dynamics 365 for Operations production environment.
Dynamics 365 for Operations is supported according to the Microsoft Modern Lifecycle policy, which provides consistent and predictable guidelines for product support availability.
Wednesday, 5 April 2017
Chnage Session date in Microsoft Dynamics AX 7/365
Accountants would like to easy enter corrections at a month end date. For this reason in previous versions of Microsoft Dynamics AX there was an option in the Tools menu to change the session date and time. However this menu is not implemented in the new cloud based Dynamics AX, the option to change the current work date is still available. The option is even closer than you might think.
Session date
When you need to process a lot of transactions on a certain date, you can select another date to be defaulted on e.g. general journal lines. This might be a month end date, but also any other date. In the new Microsoft Dynamics AX you can access this option in two ways:
- Date selection on dashboard Calendar control.
- Date/time selection in the Session date and time form.
Calendar control
When Dynamics AX is opened, you will find a calendar control on the left. At startup is will be defaulted with the system date.
You can just select another date on this control to change the session date. A confirmation will be prompted to the user.
When the session date is changed, the current date and the session date both are highlighted on this calendar control.
To take advantage of this you can create e.g. a new general journal and edit the lines. You will notice that the session date will be used as default for the new journal lines.
Session date and time form
You can also change the session date by using the form Session date and time. This can be required if you also need to change the session time. Another (temporary) reason can be found at the end of this document. To open the form, click Menu > Common > Common > Session date and time.
You can then change the session date and or time. To confirm this action you must click the OK button at the bottom of this slider form.
There is more…
Currently in the Technical preview (CTP8) there is an issue when you want to select a date in another year.
So when you want to select e.g. December 31, 2015 while the computer date is in 2016, the wrong date is compiled to be your session date. The month and date is correct, but it is taken the current year (2016). So please check the proposed date carefully before accepting a wrong one.
Changing the date using the Session date and time form to another year is working, so there is a workaround for this issue. I have created Connect feedback to have Microsoft aware of this.
Subscribe to:
Posts (Atom)