Skip to main content

Download Source not permitted even when configuration allows downloading source

Introduction:

In this blog, I will be sharing my experience with Customization Extensions related to Download Source in Microsoft Dynamics 365 Business Central.

Pre-requisites:

  • Microsoft Dynamics Business Central On-Premise

Demonstration:

As a requirement, some customers will always request access to their Customization Extension in Business Central. One such incident happens when the project in VS Code has the Download Source enabled and Business Central did not allow Downloading the source.


After checking the code base, it was clear that Download Source is only allowed for apps where Tenant Visible boolean is set to true

In order to deploy the extension with the Tenant visible as TRUE we had to deploy the Extension App with tenant details using the PowerShell command below.
OLD COMMAND:
Publish-NavApp -ServerInstance Servicename -Path NewAppPath -SkipVerification

NEW COMMAND:
Publish-NavApp -ServerInstance Servicename -tenant default -scope Tenant -Path NewAppPath -SkipVerification

This helped me Published the Extension scope as PTE instead of Global in Business Central and I was able to Download the Source Code


Acknowledgments: Thanks to Mahekdeep Kaur and Saurav Dhyani for their help in this resolution

Conclusion:

To download the source code in Business Central, you need to ensure that you have deployed the extension as PTE and allowDownloading source enabled.

I hope this helps!!

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

Setting up OAuth Authentication for Business Central Web Services / APIs

Introduction: After upgrading Business Central to version 17 (Wave2 2020), I found that there was an error telling me that WebService Key is going to be deprecated soon. Web Service Access Key is deprecated. Hence, I decided to explore and probably make it easier through this blog. Pre- requisites : Admin Access to Office 365 Admin Access to Azure Demonstration: 1. App Registration on Azure Portal: To enable OAuth authentication for any apps in Azure Active Directory, you will need to perform App Registration and set up the permissions and security details. i.) Register the App: Search for 'App Registration' on the Azure Portal. Click on New Registration Type in the App Names, Account Types and Redirect URI. Registering Application ii.) Setup API Permissions: Go to API Permissions > Add Permissions > Business Central App > Select Delegated Permissions > Select Other Permissions and Financials > Add Permissions Button. Setup API Permissions iii.) Setup Client Secr

Business Central Environment Blinking after update to v20

Introduction: Business Central Updates after updating to version 20.x, there is a common problem which is observed. The Business Central environment starts blinking as per the video below - Pre- requisites : Business Central Online  v20 Demonstration: 1. Restart the Business Central Environment: Go to Business Central Admin Center > Select the Environment >Sessions > Restart Environment. 2. Ensure that your URL contains Tenant ID: When you login into the Business Central Environment, make sure that your links are in the following formats Sandbox : https://businesscentral.dynamics.com/<SandboxEnvironmentName>/?sandbox=true Production : https://businesscentral.dynamics.com/<ProductionEnvironmentName>/ If you URL like https://businesscentral.dynamics.com/SandboxName or any other format without Tenant ID, chances are that you will end up with the issue. Also, you can login through Admin Center URL -  Connect from URL in BC Admin Center 3. Check the status if the insta