By default, Microsoft Dynamics NAV 2015 is set up so that you get a warning message when you enter sales invoice lines with items that are not on stock.

In this scenario, you will learn how to disable this warning in the Sales & Receivables Setup window.

On the Role Center, on the Home tab, in the Setup group, choose Setup.
On the drop-down menu, choose Sales & Receivables Setup.

In the Sales & Receivables Setup window, deselect the Stockout Warning check box.

Choose the OK button

You will now no longer get warnings on sales invoice lines for items that are not on stock.

Functional Tips

Preventing Posting of Sales Invoices that Are Not on Stock – in Navision 2015

July 29, 2015July 29, 2015 Ashwini Tripathi

By default, Microsoft Dynamics NAV 2015 is set up so that you are allowed to post sales invoices that contain items that you currently do not have on stock.

You can change that behavior to allow posting an invoice only if all the items on the lines are on stock. In this scenario, you will learn how to do it through the Inventory Setup page.

On the Role Center, o the Home tab, in the Setup group, choose Setup.
On the drop-down menu, choose Inventory Setup. The Inventory Setup window opens.

In the Inventory Setup window, select the Prevent Negative Inventory check box.
Choose the OK button..

Functional Tips

Correct a Posted Sales Invoice in Nav 2015

July 29, 2015 Ashwini Tripathi

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 Custom Word Layout for Document Reports in Navision 2015

July 17, 2015 Ashwini Tripathi

Open the MS Office Word.

File -> New and type Invoice in search and press enter to list available Invoice Templates.

In my example I am using [Sales Invoice (Blue Border Design)]

Select Create to download the template and create a document for you.

Your new document created from this template will look as below:

Prepare the Layout by removing extralines as we will be using repeating lines for Lines.

Save your Template.

I have made a copy of Report 206 – Sales – Invoice on new ID say (50005 as Sales – Invoice Word).

This report dosen’t have Word Layout. We will be creating one Customize Layout form above saved Invoice above. [Sales Invoice (Blue Border Design)]

Open Report Layout as shown in below Screen:

Slect the Report and choose Custom Layout as shown in above screen.

In Custom Report Layout Window Click on New.

From window Insert Build-in Layout for Report Select Insert Window Layout and click OK button.

From Custom Report Layout window Select Import Layout, Select your word file prepared above and Respond Open to Import.

Then, press Edit Layout and prepare layout on Developer tab, find XML Mapping Pane and find your document in Custom XML Part.

Now, you can find all fields from Dataset.

Please see below links to complete your report:

Adding image fields

Add fields from a report dataset to a word report layout

Creating my first word list report in Navision 2015

How to specify the default built in report layout

Create a word report layout for a report

Once you are done with your field assignment close the word layout.

Select Yes to import changes to the report.

Select Run Report to view the output of your report.

Now you are done with your Custom Report Layout.

Please see sections which will be more helpful to complete your task:

Reports

Uncategorized

Useful Tips for Technical as well as Functional (Saving Customer/Vendor/Item as Template)

July 15, 2015July 15, 2015 Ashwini Tripathi

Normally we see Template is created at on Interface and the Customer/Vendor/Item are created via other interface.

We can make it more user friendly, in below article I will show some readymade tips available in Navision It is available in 2013 and 2015, for lover version please verify accordingly.

First Lets have a look at what all is available to us then we will see how we can make the more meaningful to our customers. Obviously if any out of box customization is required that we have to carry out.

Others too available check it out, I will show one of them rest you apply same skill to accomplish others.

Let’s Start with Page 1300 Mini Customer Card what it looks like.

In this Page on Action Tab we have Save as Template the functionality which we are going to use in our Article for today.

Let’s First Link this Page (1300) with our Std. Customer Card Page (21).

I will Add New Action on my Page and set following Properties.

Open the Page 21 in Design Mode & Access View -> Page Actions.

We have added this Link Just for information you can Skip this step, it is not compulsory for what we are going to perform below in next step.

Here other tabs of Mini Customer Card is only visible following certain Conditions. So nothing wrong with code or design. Technical can review the code and find out the reason for same.

Like :

Next we will copy one Functionality from Page 1300 to our Page 21. Save as Template.

Open the Page 1300 in Designer and access to View -> Page Actions.

Save the object no further any coding or Variable definition will be required. As this Functionality is properly designed as plug and Play. Required Variables are defined local and it takes the Current Record as Parameter.

TempMiniCustomerTemplate.SaveAsTemplate(Rec);

Now Open your customer card, scroll to record which you want to save as Template and Select Save as Template from Action Tab. Give the Template name to save and click OK.

Your Template is saved. Now you can use the same to apply to your New Customer.

Now Create New Customer and Select Template to Apply.

You are done.

This way you are able to give something new to your Customer without any major customization.

Similarly you can do for Item & Customer too.

Explore there are few more which will be helpful in certain conditions.

Tag: MS

Disabling the Stockout Warning Message – in Navision 2015

Preventing Posting of Sales Invoices that Are Not on Stock – in Navision 2015

Correct a Posted Sales Invoice in Nav 2015

Create a Sales Invoice for a new Customer

UpdatePropagation Property

Data Upgrade Codeunit in Navision 2015 – Part -2

Conclusion

Data Upgrade Codeunit in Navision 2015 – Part -1

Schema Synchronization in Microsoft Dynamics Navision 2015

Creating Custom Word Layout for Document Reports in Navision 2015

Useful Tips for Technical as well as Functional (Saving Customer/Vendor/Item as Template)

Rate this:

Share this with:

Rate this:

Share this with:

Rate this:

Share this with:

Rate this:

Share this with:

Rate this:

Share this with:

Conclusion

Rate this:

Share this with:

Rate this:

Share this with:

Rate this:

Share this with:

Rate this:

Share this with:

Rate this:

Share this with: