Advertisements

The first look at the next generation of intelligent business applications in the cloud. Dynamics – 365

 

Today I had a chance to attend Dynamics 365 – first look presentation from Microsoft.

Below are the few takeaways from this session, sharing with you, will come up with more details later in my upcoming posts.

Microsoft Dynamics 365

Enable your organization to grow, adapt, and evolve to meet the needs of your customers with Dynamics 365 – the next generation of intelligent business applications.

 

1

 

14

 

15

Use digital intelligence to reimagine what’s possible for your business.

Dynamics 365 unifies CRM and ERP capabilities into applications that work seamlessly together across sales, customer service, field service, operations, financials, marketing, and project service automation.

Start with what you need, add applications as your business grows.

Rethink what’s possible for your business when you:

  • Better engage customers
  • Empower employees
  • Optimize operations
  • Reinvent products and business models

23456789101112

Product demo was also given, will share those details also in my upcoming posts. Till then keep exploring and learning.

All screenshots are taken from Microsoft presentation.

You can find more details and explore on below link: https://www.microsoft.com/en-us/dynamics/default.aspx

13

 

Advertisements

Upgrading the Application Code in Microsoft Dynamics NAV 2016

Continuing from my earlier post Upgrade in Microsoft Dynamics NAV 2016

No doubt typically, customers want all the customizations that have been implemented in their existing Microsoft Dynamics NAV databases to be migrated to their new Microsoft Dynamics NAV 2016 databases.

Depending on the version of Microsoft Dynamics NAV that a database is being upgraded from, the amount of code changes between the two versions is large or small.

To upgrade the application code, you must merge code from different versions of the application. This merge process is known as a code upgrade or application upgrade.

You must upgrade the application before you upgrade the data.

Application Upgrade Overview

You must analyze and process code changes by comparing and evaluating three separate versions of the Microsoft Dynamics NAV database:

Version Description
Original version This is the baseline version of the solution that you want to upgrade, such as the original release of Microsoft Dynamics NAV 2013.
Modified version This is the version that you want to upgrade, such as a customer’s database with customizations and add-on solutions.
Target version This is the target of the merge process that you want to upgrade your application to, such as the standard version of the Microsoft Dynamics NAV 2016 database.

When you merge the application objects from these three versions, you can import the result into a new Microsoft Dynamics NAV 2016 database that then contains the upgraded application.

At the end of the process, you export the merged Microsoft Dynamics NAV 2016 objects from this database to a .fob file that you will use during the data upgrade.

The following list describes the main steps of upgrading the application code:

  • Prepare the application object text files.
  • Merge versions.
  • Resolve conflicts
  • Import and compile the merged application objects.
  • Export all objects.

To begin, create five folders on the computer and name them as follows:

In my example, the UpgradeDemo folder on the C drive contains five folders: ORIGINAL, MODIFIED, TARGET, DELTA, and RESULT. The DELTA and RESULT folders are empty. The ORIGINAL, MODIFIED, and TARGET folders contains one or more text files that contain application objects.

Preparing the Text Files

The Microsoft Dynamics NAV cmdlets take text files as input. You must prepare three sets of text files that contain application objects as describes in the list above. You can export application objects to text files from the development environment, or by running the ExportObjects command. The following list describes the main steps of preparing the text files that you must provide as input for the application merge process.
Upgrade2016-15

  • First, export all application objects from the original version, such as the original Microsoft Dynamics NAV 2013 R2 database. Do not export system tables. Name the file OldBaseVersion.txt, and then save the file in the ORIGINAL folder that you created earlier. For example, the Microsoft.Dynamics.Nav.Model.Tools.psd1 module includes a function, Export-NAVApplicationObject, that runs the ExportObjects command. This means that you can run a command such as the following:

Export-NAVApplicationObject –DatabaseServer MyServer –DatabaseName “Demo Database NAV (7-1)” –Path C:\Upgrade\ORIGINAL\OldBaseVersion.txt

  • Next, export all relevant application objects from the modified version, such as the customized Microsoft Dynamics NAV 2013 database. Do not export system tables. Name the file OldCustomVersion.txt, and then save the file in the MODIFIED folder that you created earlier.
  • Finally, export all application objects from the new base version, such as the original Microsoft Dynamics NAV 2016 database. Do not export system tables. Name the file NewBaseVersion.txt, and then save the file in the TARGET folder that you created earlier.

Optionally, you can use the Split-NAVApplicationObjectFile cmdlet to split each text file into separate text files for each application object. This can make it easier to keep track of the process. The end result at this stage is three folders with one or more text files that contain the three sets of application objects that you want to merge.

To compare two sets of application objects

  • Open the Microsoft Dynamics NAV 2016 Development Shell in administrator mode.
  • Navigate to the location of your folders by typing a command such as the following:

cd c:\UserData\UpgradeDemo  (in my case)

  • To run the cmdlet to compare all application objects in the ORIGINAL folder to the application objects in the MODIFIED folder, type the following command:

Compare-NAVApplicationObject -OriginalPath ‘C:\UserData\Upgrade Demo\Original’ -ModifiedPath ‘C:\UserData\Upgrade Demo\Modified’ -DeltaPath ‘C:\UserData\Upgrade Demo\Delta’

Upgrade2016-16

Upgrade2016-17
This generates a number of DELTA files that describe the difference between ORIGINAL and MODIFIED. You can open the DELTA files in text editors such as Notepad. The following example illustrates how a DELTA file identifies the difference between ORIGINAL and MODIFIED.
Upgrade2016-18
Let us understand how the changes are reported when we compare the objects.
Upgrade2016-19

Upgrade2016-20

You can apply those differences to TARGET by using the Update-NAVApplicationObject cmdlet.

To apply DELTA files to application objects

  • Open the Microsoft Dynamics NAV 2016 Development Shell in administrator mode.
  • Navigate to the location of your folders by typing a command such as the following:

cd c:\UserData\UpgradeDemo  (in my case)

In this example, the folder structure is the same as described above procedure. You can now run the cmdlet.

  • To run the cmdlet to apply the differences that are stored in the DELTA folder to the application objects in the TARGET folder, type the following command:

Update-NAVApplicationObject –DeltaPath ‘C:\UserData\Upgrade Demo\Delta’ -TargetPath ‘C:\UserData\Upgrade Demo\Target’ -ResultPath ‘C:\UserData\Upgrade Demo\Result’

Upgrade2016-21

Upgrade2016-22

This merges the difference between ORIGINAL and MODIFIED with the target solution and puts the resulting solution in the RESULT folder.

You can now import the merged objects into a Microsoft Dynamics NAV database.

Merging Versions

Alternatively to above process you can merge the three sets of application objects to create the application for the new database.

You can use the Merge-NAVApplicationObject cmdlet to merge the three sets of application objects.

The following example illustrates the type of command that you can run.

Merge-NAVApplicationObject -OriginalPath ‘C:\UserData\Upgrade Demo\Original’ -TargetPath ‘C:\UserData\Upgrade Demo\Target’ -ModifiedPath ‘C:\UserData\Upgrade Demo\Modified’ -ResultPath ‘C:\UserData\Upgrade Demo\Result’

Upgrade2016-23

Upgrade2016-24

Depending on the number of objects that you are merging and the number of differences found, this can take a few seconds, a few minutes, or longer.

The RESULT folder will contain a text file for each application object. The result of the merge is shown when the cmdlet completes, including a description of any application objects with conflicting code.
Upgrade2016-25

These conflicts are stored in .CONFLICT files in the RESULT folder. You can import all objects in the RESULT folder into the new Microsoft Dynamics NAV 2016 database, or you can analyze the conflicts before you import the objects.

Handling Conflicts

Depending on the application that you are upgrading, you can choose to analyze the conflicting code before you import the merged objects into the development environment.

The conflicts are shown in the merged text files but are also identified in .CONFLICT files in the RESULT folder. Subfolders then contain copies of the source files from the versions that have conflicting code.
Upgrade2016-26

You can analyze the conflicts in any tool, make the relevant changes, and then run the merge operation again. Alternatively, you can import the merged files into the development environment, and resolve the conflicts there.

Importing and Compiling Merged Objects

After you have completed the merge, import the new custom version into the new Microsoft Dynamics NAV 2016 database, and then compile all objects. You must resolve any compilation errors before you can continue.

The text files with the merged application objects include successfully merged code, and code that is partially merged. You can import the partially merged objects into the Microsoft Dynamics NAV 2016 development environment and resolve the conflicts there.

You can use Import-NAVApplicationObject, that runs the ImportObjects command.

This means that you can run a command such as the following:

Join-NAVApplicationObjectFile -Source ‘C:\UserData\Upgrade Demo\Result\*.txt’ -Destination ‘C:\UserData\Upgrade Demo\FinalMergedObjects\all-merged.txt’

Upgrade2016-27

First we will join the many text files into a single file using above command and as a result we get all-merged.txt file which we will import in database using below command.

Import-NAVApplicationObject –DatabaseServer MyServer –DatabaseName “My Upgraded App” –Path C:\Upgrade\all-merged.txt

Now we import objects obtained from previous step into an existing, empty database.
Upgrade2016-28
When you compile the objects, an error is thrown for each code conflict, and you can use the tools that are available in the development environment to resolve the conflicts.

You now have a new database with a fully upgraded application.

Exporting All Objects

Now, you must export all objects to an objects.fob file so that you can import them when performing the data upgrade. The export must include customized objects, upgraded reports, and all other Microsoft Dynamics NAV 2016 objects.

This completes the upgrade of the application code. Next, you must upgrade the data in the database.

However you are free to do object merge and upgrade as you do earlier, here I concentrated using Dynamics Navision 2016 Development Shell. As this is the new way also much faster than what we used to do earlier.

We can use this in identifying the Objects under different categories like Modified, having conflicts and New Objects which can help in estimating also and planning the action in advance.

I will come up with further step and more details in my upcoming posts.

What’s New: Application Changes for Microsoft Dynamics NAV 2016

NAV2016
Below are the details new features and functionality that are available in Microsoft Dynamics NAV 2016 and have been added to the product since Microsoft Dynamics NAV 2015.

Will come up with detail later in my future posts.

The following features and functionality for application users have been introduced since Microsoft Dynamics NAV 2015.

Workflow

You can set up and use workflows that connect business-process tasks performed by different users. System tasks, such as automatic posting, can be included as steps in workflows, preceded or followed by user tasks. Requesting and granting approval to create new records are typical workflow steps.

Imp Note

The Document Approvals feature that existed in the previous version of Microsoft Dynamics NAV is removed. The standard approvals scenarios that were supported in the previous version are now supported as workflows for sales approvals and purchase approvals respectively.

The upgrade tool will recreate document approval data in previous versions as workflow data in Microsoft Dynamics NAV 2016.

Electronic Documents

As an alternative to e-mailing as file attachments, you can send and receive business documents electronically.

From PDF or image files representing incoming documents, you can have an external OCR service (Optical Character Recognition) create electronic documents that you can then convert to document records in Microsoft Dynamics NAV, like for electronic PEPPOL documents.

For example, when you receive an invoice in PDF format from your vendor, you can send it to the OCR service from the Incoming Documents window. After a few seconds, you receive the file back as an electronic invoice that can be converted to a purchase invoice for the vendor.

If you send the file to the OCR service by e-mail, then a new incoming document record is automatically created when you receive the electronic document back.

Incoming Documents

In the Incoming Documents window, you use different functions to review information, manage OCR tasks, and convert incoming documents to the relevant purchase and sales documents or journal lines in Microsoft Dynamics NAV.

The external files can be attached to their related document in Microsoft Dynamics NAV at any process stage, including to posted documents and to the resulting vendor, customer, or general ledger entries.

Document Sending Profiles

You can set each customer up with a preferred method of sending sales documents, so that you do not have to select a sending option every time that you choose the Post and Send button.

In the Document Sending Profile window for a sending profile, you can select the Default check box to specify that the document sending profile is the default profile for all customers, except for customers where the Document Sending Profile field is filled with another sending profile.

Posting Preview

On every document and journal that can be posted, you can choose the Preview Posting button to review the different types of entries that will be created when you post the document or journal.

Deferrals

Revenues for services or goods delivered over multiple accounting periods are not necessarily recognized in the accounting period in which the sales document is posted and payment is received. To distribute revenues on the involved accounting periods, you can set up a deferral template for the resource, item, or G/L account that the revenues will be posted for. When you post the related sales document, the revenues are deferred to the involved accounting periods, according to a deferral schedule that is governed by settings in the deferral template and the posting date.

Microsoft Dynamics CRM Integration

Microsoft Dynamics NAV 2016 introduces a new and improved integration with Microsoft Dynamics CRM.

Hiding/Showing Columns on Microsoft Dynamics NAV Web client and Microsoft Dynamics NAV Tablet client

With Microsoft Dynamics NAV it is possible to hide and show columns on the Microsoft Dynamics NAV Web client and Microsoft Dynamics NAV Tablet client, in the same way as on the Microsoft Dynamics NAV Windows client.

Freeze Pane

Microsoft Dynamics NAV now supports freeze panes on the Microsoft Dynamics NAV Web client and the Microsoft Dynamics NAV Tablet client.

Improvements on Lookups in the Microsoft Dynamics NAV Web client

With this release the Microsoft Dynamics NAV Web client offers an inline lookup experience on fields as well as the ability to do cross column search as you type in the lookup and selecting data in the lookup using the keyboard.

Microsoft Social Engagement

Microsoft Dynamics NAV integrates with Microsoft Social Engagement and can be made available on customers, vendors, and items.

Cross Column Search on the Microsoft Dynamics NAV Web client

In Microsoft Dynamics NAV Web client it is now possible to search across columns in a list. This search is activated by choosing the Search icon, and entering the search criteria. The search offers filter-as-you-type functionality, and will look for records that contain the search criteria. Symbols can also be used in the search criteria, and the search criteria are then interpreted exactly as you entered it.

Navigation Pane and Cues

Previously the navigation pane contained list places that were auto generated based on the available cues in the Role Center. These list places no longer get auto generated by default. Only if there is a relevant entity in the navigation pane, a list place will be created.

Entering Dates in the Microsoft Dynamics NAV Web client

In Microsoft Dynamics NAV Web client and Microsoft Dynamics NAV Tablet client you can now use the date lookup functionality on lists instead of typing dates in manually.

Control Add-ins on Microsoft Dynamics NAV Phone client

On Microsoft Dynamics NAV Phone client you tap on control add-ins to zoom

Selecting Company, Language, Region, Time Zone and Work Date in Mobile Clients

With the new My Settings page, it is now possible to dynamically switch the UI language, region, time zone, company, and work date of the Microsoft Dynamics NAV Web client, Microsoft Dynamics NAV Tablet client, and Microsoft Dynamics NAV Phone client.

Multiple Selection of Lines in Microsoft Dynamics NAV Web client

You select multiple lines in the Microsoft Dynamics NAV Web client by activating the context menu on a line, and then choosing Select More. When you choose Select More, a checkbox for selecting all rows is placed right above all the rows.

Updating and Testing Multiple Custom Report Layouts

Instead of updating custom report layouts to dataset changes one layout at a time, you can now perform an update of all custom layouts at once.

You also have the option to test updates without applying the required changes to the custom report layouts. This enables you to see what changes will be applied to the report layout and identify possible issues in the process.

Important

Most of the contents you find in this blog will be either inherited from MSDN or Navision Developer IT Pro Help. Some places images are also directly taken from these sites. Purpose is simple to try those stuffs and re-produce adding few things as per my understanding to make easy understanding for others and quick reference.

Here nothing under my own brand or authorship of the content. At any point of time we are just promoting Microsoft stuffs nothing personnel with same.

Hope stuffs used here will not violate any copyright agreement with them. In case by mistake or in-intestinally it happens and the Microsoft feels these should not be used Microsoft have full right to inform me about same and will be glad to take down any such content which may be violating the norms.

Purpose is to promote Navision and share with community.

FB Profile

Like FB Page

%d bloggers like this: