@eHougaard @drimmelzwaan a long time ago, there were not as many great ways to extend the base application as there are today. it was very easy to bring your solution into the saas using the lift & shift principle. please keep in mind that embed program is older than microsoft base app.
@TineStaric@waldo1001 imho thats bad practice. Why not open the required internal procedures for others? maybe some other customer or VAR could need them!
New Blog Post: "Isolated Storage is no guarantee of security" aka. "How to hack bad isolated storage implementations"
https://t.co/uKEFcM5M5f
#msdyn365bc
@TineStaric Don't do it! Internal visibility is great to allow test apps to dive deeper in the code as other apps. You should move your GetPassword Proc to where it's needed and set it local.
@KarolakNatalie That's not the only bug. We also found some issues when moving an action from a page to a pageextension in the same app. The upgrade of other apps will fail when they reference this action. Msft told us this is by design.
Breaking Pipelines in 3, 2, 1 ...
#msdyn365bc support comment in a json file. the only problem is that this is not provided for in the json specification and #powershell does not support it either.
#BCLaunchEvent
@KarolakNatalie at first glance, i don't think this is a good thing. since pretty much all devops solutions used the bccontainerhelper as a basis, a change was easier and had many synergy effects.
let's see what the future brings
@SBalslev Holy moly. AL will be more and more a high-level language. The fast changes are more and more challenging to the dinosaur devs. Time to evolve or extinct.