Posts are filtered by Author (Andrius Čyvas). Click here to see all posts.

Clarified Rules for Dynamics 365 Business Central Per Tenant Extensions and AppSource Apps Lifecycle

Dynamics Partners who have Dynamics 365 Business Central Extensions on Microsoft AppSource, and resellers who provide Per Tenant Extensions (PTE) in Dynamics 365 Business Central SaaS must align the code with the Microsoft release cycle within set deadlines. An inability to make code compatible and meet the deadlines can cause a serious disruption for the Dynamics Partners and impact end-customer business continuity. Read on to find out more.

What to Expect When Moving Your Solution to Dynamics 365 Business Central SaaS and AppSource [2]

This is the second part of a two-part blog series on “What to Expect When Moving Your Solution to Dynamics 365 Business Central SaaS and AppSource”. In Part 1 of the blog series the technical differences were covered. In this blog, I will cover the costs and operational differences of maintaining customer and ISV Business Central SaaS solutions vs. Business Central On-Premises solutions.

What to Expect When Moving Your Solution to Dynamics 365 Business Central SaaS and AppSource [1]

Dynamics 365 Business Central continuously evolves and with each major release comes the long-awaited features. Customizing Business Central through Extensions, eliminates the need to modify the Dynamics 365 Business Central standard code to implement additional functionality and enables the transition to cloud-ready solution. However, the rapid Business Central evolution also brings side effects that Dynamics Partners should be aware of and plan for accordingly. Taking this into account, I’ve created this blog to provide details on the impact of common changes from a technical perspective.

Speed Up The Transition From C/AL to Extensions

The technological changes in the Microsoft Dynamics 365 Business Central SaaS market require a lot of preparation from Microsoft Dynamics Partners. Dynamics Partners often struggle to understand the level of disruption and the resources required to successfully adapt. Thus, when transitioning from C/AL to Dynamics 365 Business Central Extensions, Dynamics Partners often look for an experienced consultant or solution architect who can help to analyze Microsoft Dynamics NAV solutions. It usually takes around 2-3 weeks to figure out how big the changeover to an Extension can be, which is time consuming and costly; an exercise that can often result in delays to the project.

Choosing the BestPath for Extensions to Dynamics 365 Business Central

As a Microsoft appointed ISV Development Center, 1ClickFactory, renowned for its upgrade tools and expertise is honored to efficiently support technological transformations to Dynamics 365 Business Central Software-as-a-Service (SaaS). From numerous interactions with Dynamics Partners, we’ve learned that a number of Dynamics partners have embraced an isolated approach to development practices.

The Push to Extensions 2.0: What It Means for You!

One of the biggest cost drivers for Partners and their customers, since the introduction of add-ons in the mid-1990’s, has been the cost of managing and upgrading these add-ons in customer solutions to keep up with Microsoft’s numerous releases. This has become an even greater issue with the release of the newest version of Dynamics 365 (NAV / AX).