You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For development we are using containers & Azure VMs with sandbox artifacts. So we are as close as production environment, and all SaaS functions (for e.g. IsSaaS), are working correctly.
Recently, we came to one annoying limitation of using sandox artifacts. Apparently, it's not possible to debug background sessions for sanbox environments. This make completely sense for production, but for local(& cloud) dev/test environments it doesn't. To my opinion, debugging background sessions should be allowed for nonprod environment, otherwise the purpose of using sandboxes for dev & testing looses it's meaning.
Best Regards,
Gintautas
The text was updated successfully, but these errors were encountered:
This is a feature request, so it will have to go through our prioritization for new features. You can post this to our Ideas forum at https://aka.ms/BusinessCentralideas, or vote up the idea if its already there. We're constantly monitoring top Ideas and will consider them for a future release.
hey @thloke,
Can you please confirm that it's not possible to enabled debugging background session for container created with sandbox artifacts? Perhaps there's navserver settings that we could use to enable it?
Hey AL gurus,
For development we are using containers & Azure VMs with sandbox artifacts. So we are as close as production environment, and all SaaS functions (for e.g. IsSaaS), are working correctly.
Recently, we came to one annoying limitation of using sandox artifacts. Apparently, it's not possible to debug background sessions for sanbox environments. This make completely sense for production, but for local(& cloud) dev/test environments it doesn't. To my opinion, debugging background sessions should be allowed for nonprod environment, otherwise the purpose of using sandboxes for dev & testing looses it's meaning.
Best Regards,
Gintautas
The text was updated successfully, but these errors were encountered: