87
In the old development environment, the debugger could be attached to any instance, or selectively to the next started instance. This was very useful. Currently it seems it is not possible in D365 Business Central.

If something unexpectedly goes wrong in a customer’s production environment, we must be able to trace the origin of the error, to be able to fix it. Bugs are sometimes environment, data or user sensitive, and very difficult to reproduce. If we cannot debug a specific instance of BC, we might be unable to help our customer, or it may take a tremendous amount of unnecessary work.
Category: Development
STATUS DETAILS
Under Review
Ideas Administrator

Thank you for your feedback. We are having this in our longer term roadmap. Please continue to vote. 

Best regards,
Business Central Team

Comments

T

This is very useful for user support

Category: Development

T


Debug mode is vital to know what a user has done at the time an error appears. Highly necessary not only for development, but for the administration of the application in companies.

Category: Development

T

El modo de depuración es vital para saber que ha hecho un usuario en el momento que aparece un error. Altamente necesario no tan solo para desarrollar, sino para la administración de la aplicación en empresas.

Category: Development

T

Must have!

Category: Development

T

O M G
We need this

Category: Development

T

Must have!

Category: Development

T

Yes, definitely need debugging tools that will work in all scenarios.

Category: Development

T

I'm also in need of this feature: I'm currently doing an implementation using the new API's and the only way I found to debug the calls is to use the "old" debugger.

In my opinion a new environment should at least provide the same feature as the old...

Category: Development