Select Page

Summary of Cumulative Update For Microsoft Dynamics NAV – October 2018

Hi,

Please find more information about Cumulative Update for Microsoft Dynamics NAV released in October 2018 below.

Here you can find the download links.

Cumulative Update 10 for Microsoft Dynamics NAV 2018 has been released (Build 24742)

Download Link

Cumulative Update 23 for Microsoft Dynamics NAV 2017 has been released (Build 24745)

Download Link

Cumulative Update 36 for Microsoft Dynamics NAV 2016 has been released (Build 50637)

Download Link

Cumulative Update 48 for Microsoft Dynamics NAV 2015 has been released (Build 50638)

Download Link

Microsoft Dynamics Business Central on premises is available now

On October 1st, Microsoft releases Microsoft Dynamics Business Central on premises.

With this latest release, Microsoft Dynamics NAV is renamed Microsoft Dynamics 365 Business Central on premises to be united under the Dynamics 365 Business Central brand. Dynamics NAV customers upgrading to Business Central on premises will enjoy the unique flexibility to continue running on premises, move to the cloud, or adopt a hybrid approach.

Download link : https://mbs.microsoft.com/partnersource/northamerica/support/support-news/bconpremdownload

Currently it is available for 23 countries including World-wide version. See below list.

Australia Austria Belgium Canada
Czech Republic Denmark Finland France
Germany Iceland Italy Mexico
Netherlands New Zealand Norway Spain
Sweden Switzerland United Kingdom United States
North America Russia W1  

Stay tuned for What’s new and more information…

Summary of Cumulative Update For Microsoft Dynamics NAV – September 2018

Hi,

Please find more information about Cumulative Update for Microsoft Dynamics NAV released in September 2018 below.

Here you can find the download links.

Cumulative Update 9 for Microsoft Dynamics NAV 2018 has been released (Build 24232)

Download Link

Cumulative Update 22 for Microsoft Dynamics NAV 2017 has been released (Build 24238)

Download Link

Cumulative Update 35 for Microsoft Dynamics NAV 2016 has been released (Build 50583)

Download Link

Cumulative Update 47 for Microsoft Dynamics NAV 2015 has been released (Build 50585)

Download Link

Viewing Table Data in Microsoft Dynamics 365 Business Central

In older NAV versions, developers and users(with required permissions) can view the table data by running tables directly from the Object Designer of NAV Development Environment. See below screen.

But now with Business Central we have new Modern Development Environment for AL programming. For more information, https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-reference-overview

Let’s see how we can View Table Data in Microsoft Dynamics 365 Business Central Web Client.

For developers, administrators, and support personnel, it can be useful to inspect table data in the tenant database, particularly when debugging or troubleshooting. To support this need, you can view table objects in the Web client.

  • In a production environment, administrators and support can view a table directly from the Web client.
  • In a development environment, in addition to viewing a table directly from the Web client, developers can view a table automatically when they publish/debug an AL project from Visual Studio Code.

NOTE : The table appears as read-only in the client, so modifications, insertions and deletions cannot be made.

IMPORTANT : Data in the tables can be sensitive. Be sure to follow your organization’s guidelines for handling such data.

Required permissions

Whether viewing the table directly from the client or from Visual Studio Code, your Dynamics 365 user account must have the following permissions:

  • Read permission on the table that you want to view.
  • Execution permission (direct) on the System object 1350 Run table.

Any end-user that is assigned these permissions will be able to view that table in the browser.

View a table object directly from the client

To view a table, you add the table=<TableID> parameter to the client’s address (URL), replacing <TableID> with the ID of the table that you want to view.

For example, if your URL starts with https://businesscentral.dynamics.com , then to view table 18 Customer in your current company, you could use the following URL:

https://businesscentral.dynamics.com/?table=18

Or for a specific company, such as “CRONUS Inc.”:

https://businesscentral.dynamics.com/?company=CRONUS%20Inc.&table=18

Note the use of & when table=<TableID> is not located directly after the domain name.

See below example, how we can run table object directly from the client running on docker container.

  • Home page

  • To view data in current company

  • To view data in specific company

View a table object from an AL project in Visual Studio Code

You can configure an AL project to view a table when you publish or debug the project (pressing F5 or Ctrl+F5).
In the launch.json file for the project, set the “startupObjectType” parameter to “table” and the “startupObjectId” parameter to the ID of the table. For example:

Output will be

Constraints

You cannot view virtual tables or the following system tables:

ID Name
2000000170 Configuration Package File
2000000170 Configuration Package File
2000000173 Data Sensitivity
2000000100 Debugger Breakpoint
2000000103 Debugger Watch
2000000130 Device
2000000114 Document Service
2000000190 Entitlement Set
2000000191 Entitlement
2000000180 MediaSet
2000000181 Media
2000000195 Membership Entitlement
2000000162 Nav App Capabilities
2000000152 Nav App Data Archive
2000000161 Nav App Dependencies
2000000150 Nav App Object Metadata
2000000163 Nav App Object Prerequisites
2000000142 Nav App Resource
2000000151 Nav App TenantApp
2000000160 Nav App
2000000071 Object Metadata
2000000079 Object Tracking
2000000001 Object
2000000198 Page Documentation
2000000186 Profile Page Metadata
2000000082 Report Layout
2000000065 Send To Program
2000000112 Server Instance
2000000066 Style Sheet
2000000197 Token Cache
2000000081 Upgrade Blob Storage
2000000121 User Property
2000000076 Web Service
2000000194 Webhook Notification
2000000199 Webhook Subscription

Source of Informationhttps://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-view-table-data

Deploying a Per Tenant Customizations

There are 4 ways how we can extend Microsoft Dynamics 365 Business Central.

  1. Connect Apps  (A Connect app can be used in the scenario where there must be established a point-to-point connection between Dynamics 365 Business Central and a 3rd party solution or service.)
  2. Add-On Apps  (An Add-on app extends the experience and the existing functionality of Dynamics 365 Business Central. Add-on apps can be used in multiple scenarios, whether it is to integrate to online services, making custom web services, adding business functionality, or extending the user interface.)
  3. Embed Apps  (An Embed app defines a customer scenario. Specifically, the scenario of a customer wishing to acquire an end-to-end solution meeting the specific needs of an industry vertical or a micro-vertical.)
  4. Per Tenant Customizations

First three types of apps are available through Microsoft AppSource. Today we will see how we can deploy a per tenant customization to customer’s production tenant.

When you have finished developing and testing your tenant customization, you must deploy the extension (.app file) containing the customization to your customer’s production tenant. You must be able to log into the customer’s tenant as a user with permissions to the Extension Management page to complete the deployment.

Use the Upload Extension action to deploy the extension. The extension can be deployed for the current version or for the next version of the service. In most cases it is sufficient to select the current version, unless you have developed the extension specifically for the next version.

Note

When you deploy an .app file for the next version, the extension will be queued up to be deployed as part of the customer’s tenant being upgraded to the next version. You can typically use this in a situation where you have built an upgrade of the extension to work with the next version.

The extension you are deploying could be the initial release of the customization or an upgrade to a previous version. You must use the same steps for uploading a new extension or an extension upgrade. The service will determine if the extension needs to be upgraded based on the extension’s app ID and version.

Important

If you are developing an extension as an update to a previously deployed extension, you must keep the app ID the same and increase the version to successfully upgrade the extension to the new version.

Steps for deploying your .app file

Log into your customer’s Dynamics 365 Business Central tenant.

Enter this URL : https://businesscentral.dynamics.com in web browser. It will ask for username to Sign in.

 

Press Next for the password.

After the successful login you see the Home page of Microsoft dynamics 365 Business Central.

Open the Extension Management page.

Press the search button from Right-Top corner of the Home page and type Entension Management in search                 box. Select the first option available from the results. 

Choose the Upload Extension action.

It will open Upload and Deploy Extension page.

Select the browse button to select the .app file to upload. Browse to and select the extension’s .app file.

Select if you want to deploy for the current version (most common) or Next minor version or Next major version. Select the language for the deployment.

Choose the Deploy button. You will see the below information message. Press OK to continue.

The extension will be deployed in the background.

To check the status of the deployment, choose Deployment Status and then view the status of the extension deployment. Select the row to see additional details.


In the deployment status details there is a Refresh button in the actions you must press to retrieve the most               recent status and details.

It will show status as “InProgress”.

Once it is completed status will change to “Completed”. If the deployment is fail then it will show the status as “Failed”. As of now there are no any options available to check detailed error log why the deployment is failed.

When the extension has been successfully deployed, choose the Refresh button to see the new extension in the list of installed extensions.

Click on the installed extension to see the details.

To remove the extension from the customer’s production tenant first Uninstall it and then Unpublish it. Right click on extension which you want to remove.

Select Uninstall to open Extension Uninstallation window. Press Uninstall button from the window. It will show information message about Uninstallation.

And you can see status of extension as Uninstalled in the list.

After the uninstall we need to unpublish the extension to remove.

Once it is removed successfully you can’t see in Extensions list page.

Main source of information: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-deploy-tenant-customization

Stay tuned here for more information on Microsoft Dynamics 365 Business Central…