🗞️🗞️🗞️ BREAKING NEWS🗞️🗞️🗞️ Shortly after the #MSDyn365BC BCApps GitHub repository went live, we now have a draft pull request on the brand new Business Foundation logical layer with its 1st module: No. Series 🥳 You may now start commenting on our code and let us know what you think is missing in order to make the release of this new module a roaring success 🚀 Have I mentioned how much I ♥️ this new way of working? That's transparency and partner collaboration on a whole new level 💪 Check out the code here: github.com/microsoft/BCApps/…

Looking for feedback from all Business Central developers! 👀 As a little "side project", my team is trying to improve the way we document the deprecation of #MSDyn365BC features 📖 While spiking, we’ll use simple methods to achieve our goal. If it’s a success, we might introduce new properties on objects etc. But let’s first validate the value 🪙 So, here goes: we were thinking it would be beneficial to group all object obsoletions, belonging to the deprecation of one feature, together by adding an identifier (for now just as part of the ObsoleteReason text). What do you think? Also, for the deprecation of larger features, we want to add more detailed deprecation documentation, explaining how to make the change from old to new in greater detail. We’ve come up with a first draft, where we try to explain how to make the move from the 2023 Wave 1 deprecated User Groups to the new Composable Permission Sets: go.microsoft.com/fwlink/?lin…. What do you think of the format? If helpful, a link to such article could become part of every obsoleted object belonging to that deprecation (again, for now we'll just add the URL to the ObsoleteReason). What do you think? Is this initiative 👍 or 👎. Would you need anything else to make the switch to new features in your code easier for you? Any input is greatly appreciated 😊