From the Microsoft Dynamics 365 Business Central Blogs: Universal Code initiative; Library apps; Service-to-service authentication; Data clean up

This week on the Dynamics 365 Business Central blog roundup:

• The 'Universal Code initiative'
• Dynamics 365 Business Central: AppSource submission of library apps used by different extensions
• Business Central service-to-service authentication (OAuth) and task scheduler
• A reminder for data cleanup when migrating from NAV to Business Central SaaS

The 'Universal Code initiative'

Writing on his Waldo.be blog, Waldo, aka Eric Wauters, noted that several months ago, he blogged about a new Microsoft initiative: the Dynamics 365 Business Central Publisher program. He stated that Microsoft offered more insights into the program at Directions EMEA.

Wauters wrote that although the program still has the same focus and intention, the approach and name are different.

The initiative is only there to make the Business Central community perform better in terms of creating future-proof solutions .. ANYWHERE. We’re not talking “ISV” or “Product” or “PTE” only. We’re in fact talking about ALL of them. All inclusive – isn’t that what it’s all about these days ;-).

That means anything developed for Business Central must meet a certain standard. Whenever your solution can live in the cloud, you meet that minimum requirement.

In his blog post, Wauters stated that the goal of the initiative is to encourage partners to develop and resell D365BC offerings that can live in the cloud. He then explained what Universal Code is all about, how it differs from the Publisher program, and pointed out things that could be challenging when you try to make them work in the cloud.

Dynamics 365 Business Central: AppSource submission of library apps used by different extensions

On Stefano Demiliani's blog, Demiliani stated that about a year ago he wrote about the possibility of creating library apps and submitting them on AppSource.

[A library app is] a normal extension (.app file) that your real extension (the extension you want to publish on AppSource and make it visible) depends on (dependencies setting on app.json file) and that you can submit together with your real extension. This library extension will not be visible on AppSource.