135
We need to have a database of the hotfixes that have been applied and when they were applied. If we know a hotfix is applied we can see what it relates to and then know if we start having issues of some sort after ti was applied. It is also good to know something was fixed and we may be able to remove a fix we had to do from an extension,
Category: Documentation
STATUS DETAILS
Under Review
Ideas Administrator

 Thank you for your feedback. We are considering adding it to our longer term roadmap. 
 
Your help is greatly appreciated, 
Business Central Team

Comments

K

Check this url out for BC build version and summary of the change.

https://support.microsoft.com/en-us/help/4553289/update-history-for-microsoft-dynamics-365-business-central

Category: Documentation

K

I agree with this request. We are flying blind without having a detailed list of all contents of an upcoming release (cumulative/major/patch, etc) say 30-60 days in advance. For example if you are releasing 35 changes, it would be good to know the details of all 35 well in advance, especially leading into a Preview period. if there is a place this is posted already, can you share it? if not, will there be postings going forward?

Category: Documentation

K

This is much needed. I've noticed version changes in the Base Application, and System Application (minor changes, but changes) and there are never notifications.

Category: Documentation

K

Everything that is hotfixed in BC SaaS will be included in the next Cumulative Update.

So if you published a list with hotfixes applied on BC SaaS, it would not only help partners working with SaaS customers. It would also help partners that are working with OnPrem customers. Before we submit a ticket to Microsoft support we could check this list out, then we do not waste the support resources and do not waste our own resources trying to document a repro of the issue.

Category: Documentation