Skip to main content

Checkout how Download Source Code feature on Extensions in Business Central Version 15 Production helps customers.

Problem:
A friend of mine was looking to migrate their Business Central development and support from one partner to another.
While, asking me for advice, I was evaluating what was the best solution knowing that their Business Central had customization installed and I found this which made it easy for them as their going to continue customizing Business Central from another partner.

Solution:

In Business Central version 14 Sandbox, you are allowed to Download Source Code.
But in Business Central version 14 Production, this was not the case. No Apps. could have been downloaded even though you got it developed from a Partner/ Developer and installed from them.

In Business Central version 15 Sandbox, you are allowed to Download Source Code just like you would in Business Central Version 14 Sandbox.
Download Source Code for Installed Extensions in Business Central V15 Sandbox
  And this is also the same condition  for Business Central version 15 Production tenant as well.

Download Source Code for Installed Extensions in Business Central V15 Production
Without this, the possible solution to get your app source code back from Production, you would be required to make a copy of Production into Sandbox and download it from there in Business Central Version 14.

Note: This doesn't apply to apps installed through MarketPlace.  Trust me I have tried 😜

Conclusion:
When App was installed in Business Central Version 14 Production ensured Partners / Developers that app couldn't be reused on other tenants.
This put most of the pressure on the Customers to explicitly to ask the Vendor to provide the App File.
Whereas when an App is installed on Business Central Version 15 Production, it can be downloaded and installed in another Business Central Tenants.
This means that if the Customers want to change their partners, they can seamlessly do this without having the awkward conversation of asking the code from their previous partner.

Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe