Today we will learn correct a posted sales invoice.

In previous versions of Microsoft Dynamics NAV, this required a number of steps.

This scenario demonstrates how to perform the same action in Microsoft Dynamics NAV 2015.

On the Role Centre, choose Posted Sales Invoices to open the list of posted sales invoices.
In the list of posted sales invoices, select the sales invoice that you posted in previous post, if not done click here to see the process we followed in earlier post.
On the Home tab, in the Manage group, choose View.
On the Home tab, in the Correct group, choose Correct, and then choose the Yes button

or

The posted sales invoice is now cancelled with a credit memo. A new sales invoice has been created for you.

To open the automatically generated New Invoice that was created, choose Yes.
On the new sales invoice Perform the required changes. I am changing the Quantity in my example.

On the Home tab, in the Posting group, choose Post to post the corrected sales invoice.
Respond Yes to review the posted New Sales Invoice.

To review the Posted Credit Memo for the above Invoice Correction find as below:

We are done. It’s easy na.

Functional Tips

Create a Sales Invoice for a new Customer

July 28, 2015July 28, 2015 Ashwini Tripathi

In this session we will create a sales invoice for a new customer (Customer we don’t have in our Master).

To follow Step by Step you need to do a small setup:

Open the User Personalization and Set your Profile ID as below:

Select your Profile as “SMALL BUSINESS”

Your Role Center will look like below:

On the Role Center, choose Ongoing Sales Invoices to open the list of ongoing sales Invoices.
On the Home tab, in the New group, choose New to create a new sales invoice.
In the Customer Name field, type the name of the new customer, and then press Enter or Tab to leave the field

Create the sales invoice for the new customer.

Notice that some fields are marked with red asterisks to tell which fields must be filled.

In the pop-up dialog, choose Yes to create the new customer
In the Templates window, select Customer DOMESTIC (or as desired), and then choose the OK button.

The Customer Card window opens in edit mode. Choose the OK button to close it.

The page closes and focus is back on the sales invoice that is now updated with the customer data.
In the Sales Invoice window, on the Lines FastTab, create a new line:

Enter some line data for example : Item No.: 1001, Quantity: 10

On the Home tab, in the Posting group, choose Post.
Choose Yes.

Choose No to review the posted sales invoice, as of now we don’t require.

Helpful where we require instant Customer registration for recording the Orders. Later we will fill out rest of the details regarding Customer.

Development Tips

UpdatePropagation Property

July 28, 2015July 28, 2015 Ashwini Tripathi

Sets a value that specifies what happens when a main page with a subpage is updated.

The UpdatePropagation property is available on part controls and has two options; Subpage and Both.

If UpdatePropagation is set to Subpage, an update action will update the subpage only.

If UpdatePropagation is set to Both, an update action will update both the main page and the subpage.

This is useful if a value on the subpage changes, and you want a main page total to be refreshed automatically.

Use the UpdatePropagation property to update a main page total, when the amount on the subpage lines is updated. Add a CurrPage.UPDATE(); call, for example, in the OnValidate trigger on the subpage to have the UpdatePropagation property take effect.

Let’s do it practically how it works:

I am taking Sales Order for demo of above property.

Let’s start with adding a field in Sales Header Table

I have added Total Line Amount as Flow field to Sum Line Amount from Lines.

Next I will add this field to Sales Order Page.

If we run now and make changes in Lines the Total Line amount will not update until we refresh the Page. To enable auto refresh we will be required to add Update Propagation Property of the Subpage to Both.

After doing this if I make any changes which changes the Line Amount for the lines, The Total Line Amount in Header will get updated automatically, we will not require to refresh the page.

We are done, so simple.

Development Tips

Data Upgrade Codeunit in Navision 2015 – Part -2

July 21, 2015July 21, 2015 Ashwini Tripathi

We have seen how to create Upgrade code unit in our previous post.

Please go through it, if not seen earlier the Data Upgrade Codeunit in Navision 2015 – Part -1 here

Let us continue from where we left our previous post.

We have created the Upgrade code unit to copy the data to upgrade table while performing destructive changes to My Sales Customer table.

We removed certain fields from the My Sales Customer table and the related information was moved to UPG My Sales Customer table.

Now it’s time to move these information to actual table we create for this purpose My Detailed Customer Entry table.

Although in this example this table will be exact copy of UPG My Sales Customer table, so simply we need to copy records to My Detailed Customer Entry table.

But some time we may require to add certain more field’s value while moving the data Like Entry No, Posting date to maintain the data integrity. Like think of some Service type of information you are maintaining then the same set of record may repeat number of times on different dates, then in this case we will require to add certain fields like Entry No. and Posting Dates.

Let us assume we will be maintain data of My Detailed Customer Entry in incremental way as of situation on every transaction. Balances will be maintained as of when transaction was performed.

Although this example is not feasible or practice but still we are continuing to just see how to write Upgrade Function for such purpose.

Our today’s task is to design and run data upgrade function to move data from the upgrade table to its new location.

Now the fields are deleted from the My Sales Customer table and the data is saved in the UPG My Sales table. The next step is to create the new table where the data will reside (My Detailed Customer Entry) and move the data into that table.

Let’s create the table to be used for recording of all future Customer Balances and to accommodate the data we already had in the My Sales Customer table and which we moved into the UPG My Customer table.

In the Object Designer select the Tables button and then select New button to create a new table
Define the table layout based on the layout shown in the Screenshot.

In the Dev. Environment menu, select File-Save action to save the table.
On the Save dialogue, define ID, Name = My Detailed Customer Entry, and select OK to save the table.
Close the table editor.

We will now create a new function which will contain the code to migrate the data from the upgrade table to the new table.

Note that the FunctionType property of the newly created function is set to “Upgrade”. This is how the NAV server can later figure out which function from the upgrade codeunit it must execute.

The function marked as “Upgrade” function can call functions marked as “Normal” if necessary.

In the Object Designer select the Codeunits button, select codeunit 50000 UPGTK Codeunit and then select the Design button.
In the Dev. Environment menu, select View-C/AL Globals action and in the form which is opened select the Functions tab.
Enter the name of the function, e.g. UpgradeCustomerDetails

Select the UpgradeCustomerDetails function on the Functions tab and then select the Locals button to define function parameters.
On the C/AL Locals form, select Variables tab and add 3 local variables as shown in the Screenshot section.
Close the C/AL Locals and C/AL Globals forms to return to the C/AL Editor.

The code we add to the UpgradeCustomerDetails function will copy the data from the UPG My Sales Customer table to the My Detailed Customer Entry table and then clean up the UPG Vehicle table.

Code like the Screenshot into the UpgradeCustomerDetails function.

//>> Upgrade Code

EntryNo := 1;

WITH UpgCustomer DO BEGIN

IF FINDSET THEN

REPEAT

DetailedCustomerEntry.INIT;

DetailedCustomerEntry.”Entry No.” := EntryNo;

DetailedCustomerEntry.”Customer No.” := “Customer No.”;

DetailedCustomerEntry.”As of Date” := today;

DetailedCustomerEntry.”Last SO Value” := “Last SO Value”;

DetailedCustomerEntry.”Last Invoiced Value” := “Last Invoiced Value”;

DetailedCustomerEntry.”Total Outstanding Value” := “Total Outstanding Value”;

DetailedCustomerEntry.INSERT;

EntryNo := EntryNo + 1;

UNTIL NEXT = 0;

DELETEALL;

END;

//<<Upgrade Code

In the Dev. Environment menu, select File-Save action to save the codeunit.
On the Save dialogue select OK button.
Close the codeunit editor.

In the Dev. Environment menu select Tools – Data Upgrade – Start… action.
Agree to the confirmation dialogue.
In the Start Data Upgrade window select the OK button.

You can start the data upgrade process from the Dev. Environment, or from Microsoft Dynamics NAV 2015 Administration Shell, using Start-NAVDataUpgrade cmdlet.

The NAV server will locate all upgrade codeunits and will invoke all upgrade functions within these codeunits for all companies in the database.

If you have multiple upgrade functions in your upgrade codeunit, you can choose to execute them in parallel or in sequence. You can also choose to stop at first error, or continue execution of other functions, see the list of all failed ones, fix them and start them again using the Data Upgrade – Resume… action.

In the Dev. Environment menu select Tools – Data Upgrade – Start… action.
Agree to the confirmation dialogue.
In the Start Data Upgrade window select the OK button.

In the Object Designer select the Tables button, then select table My Detailed Customer Entry and select Run button

You can see that the data from the upgrade table was successfully transferred into the new table.

Now since our data is sitting in its right place, now we can remove objects we are using for Upgrade purpose.

Now the data upgrade is completed and we need to remove the objects used within that process.

Force-delete the upgrade table, since the data was already transferred into the new table.

Delete the upgrade codeunit to make sure the old synchronization instructions defined in it are not used by the NAV server when you decide to change the My Sales Customer table again. Alternatively (if you want to reuse the upgrade codeunit later) you can choose to change the type of the GetTableSynchSetup function to “Normal”.

Now we are done with our Upgrade project.

Conclusion

This set of demonstrations have provide you the insight, new way of running the data upgrade in Microsoft Dynamics NAV 2015 by involving the schema synchronization and upgrade codeunits.

The new approach:

Simplifies the upgrade environment, since all steps are performed by the latest version of the product.
Increases the data upgrade performance, since it is possible to parallelize execution of the data upgrade functions within the upgrade codeunit and across companies.
Reduces the amount of code to be written to handle the data upgrade, since some actions are now executed automatically by the NAV Server.
Allows data upgrade to be invoked by the NAV server, minimizing the number of manual actions which should be performed during the data upgrade.
Uses familiar upgrade toolkit design concepts (e.g. upgrade tables, upgrade functions).

Development Tips

Data Upgrade Codeunit in Navision 2015 – Part -1

July 20, 2015July 20, 2015 Ashwini Tripathi

Let us start with background preparation.

I have prepared a table with below fields and filled with some sample data.

Fill in the My Sales Customer table with demo data.

Make sure you have data in all columns, preferably create several records in this table.

Now when the fields are deleted from the My Sales Customer Table and the data is saved in the UPG My Sales Customer table, we will create the new table where the data will reside in the new version (My Detailed Customer Entry) and move that data into that table using Data Upgrade action in the Dev. Environment.

Since now my project requirement is to refactor the My Sales Customer table and delete the fields which store the information about the Sales Information (“Value” fields), we need to create an intermediate upgrade table where the data from those fields will be stored until you move it into the new My Detailed Customer Entry table.

We will perform below action:

Open the Object Designer and select table My Sales Customer
Select the Design button to open the table in the designer.
In the Dev. Environment menu, select File-Save As… action.
Change the ID value to New ID, change the Name to UPG My Sales Customer and select OK button to close the dialogue and create a copy of the table.

In table UPG My Sales Customer delete fields Customer Name, Customer Type and Credit Limit.
In the Dev. Environment menu, select File-Save action.
On the Save dialogue, set the Synchronize Schema option to “Force” and select OK button to close the dialogue.

In the Object Designer select the Codeunits button and then click New to start creating a new upgrade codeunit.
In the Dev. Environment menu, select View-Properties action to start editing the properties of the codeunit.
Change the Subtype property to Upgrade and close the Properties form.

In the Dev. Environment menu, select View-C/AL Globals action and in the form which is opened select the Functions tab.
Enter the name of the function, e.g. GetTableSyncSetup
In the Dev. Environment menu, select View-Properties action to start editing the properties of the function.
Change the FunctionType property to TableSyncSetup and close the Properties form.

Select the GetTableSyncSetup function on the Functions tab and then select the Locals button to define function parameters.
Add a parameter of DataType = Record, Subtype = Table Synch. Setup, Name = TableSynchSetup, Var = Yes.

On the C/AL Locals form, select Variables tab and add a local variable of DataType = Codeunit, Subtype = Data Upgrade Mgt.
Close the C/AL Locals and C/AL Globals forms to return to the C/AL Editor.

In the GetTableSyncSetup function, add the C/AL statement as presented on the screenshot.
In the Dev. Environment menu, select File-Save action to save the codeunit.
On the Save dialogue, define ID , Name = UPGTK Codeunit, and select OK to save the codeunit.
Close the codeunit editor.

[

//>>Data Upgrade Code

// To copy data from table My Sales Customer to UPG My Sales Customer table

DataUpgradeMgt.SetTableSyncSetup

(

DATABASE::”My Sales Customer”,

50002,

TableSynchSetup.Mode::Copy

);

//<<Data Upgrade Code

]

In the Object Designer, select the Tables button and then select the My Sales Customer table in the list of tables.
Click Design to open the table in the table designer.
Delete the following fields:
Last SO Value
Last Invoiced Value
Total Outstanding Value
In the Dev. Environment menu, select File-Save action.
On the Save dialogue, notice that the Synchronize Schema option is set to “Now – with validation” and select OK button to close the dialogue.

In the Object designer, find table UPG My Sales Customer and click Run to check if the data was copied there by the schema synchronization.

Here we are now done with the Part -1 of our exercise. Next step is to move this temp data in respective table as part of our Upgrade. We will see upgrade part in our next post.

Development Tips

Schema Synchronization in Microsoft Dynamics Navision 2015

July 18, 2015July 18, 2015 Ashwini Tripathi

NAV 2015 provides you with flexibility of deciding when and how your table changes should be synchronized with corresponding SQL tables.

What is table synchronization?

NAV 2013 R2:- Schema synchronization executes automatically on any connection to the Server.

NAV 2015:- Schema synchronization executes on demand by the Server.

Way the Synchronization works:

Per Table Synchronization
Synchronizing schema changes for all tables

Now let us see how it works:

Add/Modify/Delete Fields (change table definition) we will be prompted for Synchronizing the Schema.

It gives three options description is self-explanatory.

Some time we have to do major changes to the tables which takes lots of time to sync, we can postpone the sync process by selecting Later. Once we are done with all of our changes we can go with synchronization in one go.

We get same options.

New option Check Only….

This option will only report outcome and will not Sync the Schema.

Since we have just added new field so no risk as reported by above check.

Now I will delete one field from the table and let’s see what result comes.

Summary of the 3 options as below:

When data loss is reported while changes in table definition is referred as destructive changes.

You use upgrade codeunits when you make changes to a table definition, either from the Microsoft Dynamics NAV Development Environment or during an upgrade. Upgrade codeunits migrate existing business data from the old table structure into the new table structure. An upgrade codeunit serves the following purposes:

Provides instructions for how to handle data changes to a table during schema synchronization.
Provides the logic for migrating existing data in the business data table from the old format to the new format after schema synchronization.

A typical example of when to use an upgrade codeunit is when you remove a field from a table definition and you do not want to lose the existing data in the business data table. Instead, you want to use it somewhere else in the new application.

You implement upgrade codeunits when you make destructive changes to tables in Microsoft Dynamics NAV Development Environment. After you have created an upgrade codeunit to handle table changes, you can use it when you upgrade data from an earlier version of Microsoft Dynamics NAV to the current version. A single upgrade codeunit will typically contain table schema synchronization instructions and data migration logic for multiple tables that have changed from one version of Microsoft Dynamics NAV to another.

I will come back on this topic in another post with more details.

And many more options like PowerShell Sync with above options.

Benefits:-

Perform on demand – transparency -> As developer and system administrator, you are in control when to call the schema synchronization and how to synchronize table changes. You can invoke it, plan for it and schedule for it on a case by case basis. You can also monitor its progress and monitor the state of your database (tenant).

Not blocking other changes – productivity -> Schema Synchronization has become more granular. It can be performed per table object as well as for all table changes at once. When one table is being synchronized you are no longer blocked, and you can continue making changes to other tables.

Opened for additional instructions – flexibility -> Using upgrade codeunits you can provide input for the schema synchronization to do extra tasks, like automatically moving or copying data into upgrade tables, checking the changes or forcefully applying them where necessary. (Will come up with more details on this in my next post)

Report

Creating Word Mail Merge Report in Microsoft Dynamics Navision 2015

July 10, 2015July 10, 2015 Ashwini Tripathi

Today we will see Mail Merge feature in Word Report.

I would suggest to please go through my earlier post for creating simple List Report for better understanding as some parts I will be skipping in this post assuming you have already learned from my previous post.

Here is the Quick Link : [ Creating My First List Report in Navision 2015 ]

Lets assume ever month we require to send a Reminder Letter to our Customers for Due Payments.

Now we can design such report at customer ease.

Lets Start with creating a new Report.

Add the Data Items and desired columns as one shown below.

Add appropriate filters on Data Items, I have added [ Open = Yes, Document Type = Invoice, Remaining Amount > 0, Due Date <> ‘ ‘] you select your own as desired.

Set the Report Properties as shown in below screen.

Define Global Variables as shown in below screen.

We have Included WordMergeDataItem as Cust. Ledger Entry. This will set the table to loop for records.

Each records will be considered as New Page for the Report.

In this report we are using Include Caption which will include caption for each required columns from one defined in respective table.

Add this property for each required column.

Add the code to the Data Item Trigger to fetch Customer Information for each record.

Insert New Blank Word Layout to the Report.

Export the Layout Template and Save.

Open saved Layout Template in Word.

In below screen each component is shown, refer to earlier post Creating List Word Report, Link provided above for better understanding.

In this report Label is included as we have set property for each column to include caption.

Design the sample Letter as one shown below.

I have highlighted all the Dataset Columns/Fields in yellow.

How to add fields please refer to earlier post Creating Word List Report, Link provided above.

Now Save the Template and Import into the Report.

Here is the out put from the report as below.

Each page will contain data as per in Customer Ledger Entry Due Payment Records.

We are done !!!

You can use formatting feature of Word to add more better look to your Report as desired.

Stay tuned for more in upcoming posts.

Don’t forget to follow the Blog Site for future posts.

Report

Creating my first Word List Report in Navision 2015

July 9, 2015July 9, 2015 Ashwini Tripathi

Today we will learn creating Word List Report in Navision 2015.

Prepare the Dataset for Report as below, to keep it simple I am creating List report for Item Inventory.

I am adding one additional field for Company Logo from Company information.

Make sure you add calcfields code for Picture from Company information.

—————————————————

I have added below piece of code in [ Item – OnPreDataItem() ]

CompInf.GET;
CompInf.CALCFIELDS(Picture);

—————————————————

Place the cursor on Blank Line and open Report Properties and add DefaultLayout Property.

Next we will Add a Blank Word Layout to the Report, Step as below.

Confirm the action by responding OK to the Dialog Box.

Now Export this Blank Template

and save as docx file (MS Word File)

Open the Exported Template in Word.

Click on DEVELOPER Menu.

From Ribbon click on XML Mapping Pane.

You will now be able to see XML Mapping Pan which contains your Dataset for the Report.

Click to the Dropdown List and select entry containing your Report Name & ID.

Now you will be able to access your Dataset with Table & Fields details. As shown in below screen.

Place the cursor on top (or wherever desired) of the document to add Logo to the Report.

Select the Picture Filed from the Dataset -> Right Click -> Insert Content Control -> Picture.

See below screen for details:

You will see the Place holder for the Picture.

Now add Table with 2 Rows ( 1 for Header & 1 for Data) and 6 columns.

We have six columns in our dataset excluding Logo.

Add your Header for the table, We are using fixed Text Heading as of now but you can add captions from your dataset.

In current report I have not included we can check same in some other report posts.

Select Entire 2nd Row and Add Repeating Content Control for Item (Table).

As this will show records from the table Item we included in our Dataset.

Now in each column add your columns from Dataset as shown below.

Place your cursor in each column and choose Insert Content Control -> Plain Text.

Now our Report is almost ready.

May be the Report have data which may continue on several pages, in this case our Heading Row must Repeat on every new Page. To do this we will Select the entire 1st Row -> Right Click -> Table Properties.

Go to Row Tab of Property window and put a checkmark on option “Repeat as header row at the top of each page”

Save your Word Template an Import back in your report as shown below.

Now Save the Report and Execute it.

Here is the Output below of the Report.

We are done !!!

You can use formatting feature of Word to add more better look to your Report as desired.

Stay tuned for more in upcoming posts.

Don’t forget to follow the Blog Site for future posts.

Office Integration

OFFICE 365 INTEGRATION IN NAV 2015 – Word/Excel/SharePoint

July 8, 2015July 8, 2015 Ashwini Tripathi

If you have signed up for Office 365, Microsoft Dynamics NAV can use this service to open and save documents. For example, when you export a report to Excel and save it on Office 365, Microsoft Dynamics NAV can use Excel Online that your Office 365 account uses to open the document.

Before you can use Office 365 and SharePoint Online with Microsoft Dynamics NAV, you must configure the service in Microsoft Dynamics NAV.

If you want to use the same folder to store temporary files for all users, you must specify a shared user account. Otherwise, each user’s temporary files are stored in their personal document repository on the SharePoint site.

Let us first understand the details before we start with Setup for SharePoint Shared Folder.

Your IT can help you configuring and assigning suitable rights to access. Although you can explore and help yourself. Since we are concentrating on Navision so we will not go in details for Share point.

Just to make understand I will be only covering top level information.

In this example I assume you already have up and running site for Document Sharing in SharePoint 2013 – 365 Online.

Here I am logging in to Office 365 – Online registered by me for demo purpose. You can register for free trial to explore the same in more details.

My Opening screen looks as one below.

I select SharePoint Site to continue. Below is my SharePoint Opening screen. I will select my site which I have created for this demo and file sharing with other users in my organization.

Let us understand different parts which will help configuring our Online Document Storage Configuration in Navision 2015.

Here I am in my Folder at Lower level where all my files will be stored and shared with my other colleges.

Open “Online Document Storage Configuration” from path shown in below screen.

Specify the Service Name of your choice or use Default provided by the System.

Fill the Location to your SharePoint site: Specifies the unified resource indicator (URI) for your site on SharePoint Online, such as [https://krishnasoftwaredevelopers.sharepoint.com/MS_Nav_Documents] in my case I will use this.

Fill the Folder field which specifies the folder in the document repository for this document service that you want documents to be stored in.

This field is required. If you have not already created a subfolder in your document repository, you must create one now, and then specify it in the Folder field.

The Document Repository field includes the top-level folder in the document repository that your document service provides. The Folder field specifies a subfolder so that you can keep business documents and drafts separate from pictures and other shared documents.

For example, if the Document Repository field is set to [Documents], the Folder field can be set to [NavisionDoc] as per my example discussed above.

When a user exports data to Excel, for example, Microsoft Dynamics NAV saves the temporary file at the location that is specified in the Document Repository and Folder fields, such as

[https://krishnasoftwaredevelopers.sharepoint.com/MS_Nav_Documents/Documents/NavisionDoc]

Fill Document Repository field: Specifies the name of the document library, such as [Document]

Fill User Name field: Specifies the account that Microsoft Dynamics NAV Server must use to log on to the document service.

I would recommend that you specify a different user name than the administrative account. This helps reduce the risk of users accessing administrative settings, for example. For example, if your user name as an administrator is Administrator@KrishnaSoftwareDevelopers.onmicrosoft.com,

then the user name for Microsoft Dynamics NAV Server can be Nav@KrishnaSoftwareDevelopers.onmicrosoft.com or any of the regular user names that you have created.

On the Actions tab, in the General group, choose Set Password.

In the window that appears, specify and confirm the password for the account that you specified in the User Name field. Choose the OK button.

When you have set up the service, you can test whether that configuration is valid.

On the Actions tab, in the General group, choose Test Connection.

A message displays the result of the test.

The above message confirms we can now save documents on our SharePoint.

Let us check a sample as below:
Open the Document and Execute the report available.
While Running the Report I specify I want to Print with Microsoft Word.

Document will be generated and opened in Word – Office – 365. Temp file name is given to the file. Close the File as it is auto Saved by Office 365 Word Application.