Explore topic-wise InterviewSolutions in .

Flow field:

• It is a powerful feature of C/side DATABASE system.
• Underlying CONCEPT of SIFT that increase performance.
• Flow field data does not gets stored in the data base.

SUM Index Field Technology(SIFT):

• It is a decimal field that can be attached to key definition. Fundamental feature of Navision database that forms basis for flowfeilds. Fast calculations.

• There can be a maximum of 40 keys to a table.
• Primary key can be COMPOSED of 20 FIELDS in a record.
• Single Instance CodeUnit

Flow field:

Sum Index Field Technology(SIFT):

"ONAFTERGETCURRENTRECORD" is triggered only for the CURRENT selected record.

"OnAfterGetRecord" is triggered for ALL records that are SHOWN.

"OnAfterGetCurrentRecord" is triggered only for the current selected record.

"OnAfterGetRecord" is triggered for ALL records that are shown.

Create a NEW singleinstance codeunit. This codeunit you have to launch in Codeunit 1 FUNCTION LogInStart(). Globals :

recUserSetup : Record : "User Setup"
autTimer : Automation : 'Navision Timer 1.0'.Timer (property WithEvents=Yes)

OnRun() of your singleinstance codeunit:

IF ISCLEAR(autTimer) THEN BEGIN
CREATE(autTimer);
autTimer.Interval(3 * 1000); // test each 3 seconds
autTimer.Enabled(TRUE)
END;
CLEAR(recUserSetup);
IF recUserSetup.get(USERID) THEN ;

On Trigger
autTimer::Timer(Milliseconds : Integer)

IF TODAY <> WORKDATE THEN
IF NOT recUserSetup."User May Change WORKDATE" THEN BEGIN WORKDATE := TODAY;
MESSAGE('You may not change the WORKDATE. WORKDATE has been resetted');
END;

Create a New singleinstance codeunit. This codeunit you have to launch in Codeunit 1 Function LogInStart(). Globals :

recUserSetup : Record : "User Setup"
autTimer : Automation : 'Navision Timer 1.0'.Timer (property WithEvents=Yes)

OnRun() of your singleinstance codeunit:

IF ISCLEAR(autTimer) THEN BEGIN
CREATE(autTimer);
autTimer.Interval(3 * 1000); // test each 3 seconds
autTimer.Enabled(TRUE)
END;
CLEAR(recUserSetup);
IF recUserSetup.get(USERID) THEN ;

On Trigger
autTimer::Timer(Milliseconds : Integer)

IF TODAY <> WORKDATE THEN
IF NOT recUserSetup."User May Change WORKDATE" THEN BEGIN WORKDATE := TODAY;
MESSAGE('You may not change the WORKDATE. WORKDATE has been resetted');
END;

There is a LITTLE trick to make a field EDITABLE on a NON-EDITABLE form which is to add this code to the field you want to STILL have ACCESS to.

OnActivate() CurrForm.EDITABLE(TRUE); OnDeactivate() CurrForm.EDITABLE(FALSE);

When you're on that field the form becomes editable again &AMP; when you leave it , it once again locks down.

There is a little trick to make a field EDITABLE on a NON-EDITABLE form which is to add this code to the field you want to still have access to.

OnActivate() CurrForm.EDITABLE(TRUE); OnDeactivate() CurrForm.EDITABLE(FALSE);

When you're on that field the form becomes editable again & when you leave it , it once again locks down.

Here is the simple program inside Item Card, "Blocked - OnValidate()"

IF (Rec.Blocked = xRec.Blocked ) OR (Blocked = TRUE ) THEN EXIT;

CurrPage.UPDATE;

SMAIL.CreateMessage( ......... );

SmailSent; //Smail is Codeunit SMTP Mail.

Here is the simple program inside Item Card, "Blocked - OnValidate()"

IF (Rec.Blocked = xRec.Blocked ) OR (Blocked = TRUE ) THEN EXIT;

CurrPage.UPDATE;

Smail.CreateMessage( ......... );

SmailSent; //Smail is Codeunit SMTP Mail.

Basically both 'Movement' and Reclass can be used to adjust/reclass your ITEM ledger entries information (dimension, location, and bin).

The difference is that Movement has a proper document (RECEIPT and shipment), but your work is also increase because you need to do receipt and shipment for every item movement.

If you don't need to manage receipt and shipment, then reclass is much SIMPLER in terms of work LOAD and DATA.

Basically both 'Movement' and Reclass can be used to adjust/reclass your item ledger entries information (dimension, location, and bin).

The difference is that Movement has a proper document (receipt and shipment), but your work is also increase because you need to do receipt and shipment for every item movement.

If you don't need to manage receipt and shipment, then reclass is much simpler in terms of work load and data.

Reclass will not ALTER item CARD, It will create TWO LEDGER entries to adjust your item.

Reclass will not alter item card, It will create two ledger entries to adjust your item.

ITEM Movements are for the MOVEMENT between bins within a warehouse location where you are using Directed Put-Away and Pick

Item Reclassification is used for a variety of REASONS including:

• Movements between bins within a location with bins but is not setup as Directed Put-Away and Pick
• SIMPLE transfers between locations where shipping and receiving are not required
• dimension changes to Item Ledger Entries

Item Movements are for the movement between bins within a warehouse location where you are using Directed Put-Away and Pick

Item Reclassification is used for a variety of reasons including:

Transfer Order is a process so it involves physical good transferred from one location to ANOTHER with transit time, shipment date, RECEIVING DATES etc. ITEM reclass journal is more like an adjustment than anything ELSE.

In the older versions of Navision, Transfer Order did not exist, so the only way to transfer items from 1 location to another was the Item reclass journal.

Purchase/Sales in Item journal: it is possible to post purchases/sales without an order for it. For the moment, I don't think anyone is still using it. Everyone uses Purchase/Sales orders.

Transfer Order is a process so it involves physical good transferred from one location to another with transit time, shipment date, receiving dates etc. Item reclass journal is more like an adjustment than anything else.

In the older versions of Navision, Transfer Order did not exist, so the only way to transfer items from 1 location to another was the Item reclass journal.

Purchase/Sales in Item journal: it is possible to post purchases/sales without an order for it. For the moment, I don't think anyone is still using it. Everyone uses Purchase/Sales orders.

Virtual Tables WORK in the same WAY as normal tables with the limitation being that you cannot modify the data. Virtual Tables are not STORED in the database as normal tables, but are computed at run-time. Virtual tables cannot be EDITED through Web services even if they are editable in Microsoft Dynamics NAV.

Virtual Tables work in the same way as normal tables with the limitation being that you cannot modify the data. Virtual Tables are not stored in the database as normal tables, but are computed at run-time. Virtual tables cannot be edited through Web services even if they are editable in Microsoft Dynamics NAV.

PAGE Web Services: When a page is exposed as a Web service, a default set of operations is exposed to developers so that they can manage COMMON record handling operations such as Create, READ, Update, and Delete. Page-based Web services offer built-in optimistic CONCURRENCY management. Each operation call in a page-based Web service is managed as a single TRANSACTION.

Codeunit Web Services: Codeunit Web services provide you with the most control and flexibility. When a codeunit is exposed as a Web service, no default set of operations is exposed. You can decide which operations are available on a codeunit.

Page Web Services: When a page is exposed as a Web service, a default set of operations is exposed to developers so that they can manage common record handling operations such as Create, Read, Update, and Delete. Page-based Web services offer built-in optimistic concurrency management. Each operation call in a page-based Web service is managed as a single transaction.

Codeunit Web Services: Codeunit Web services provide you with the most control and flexibility. When a codeunit is exposed as a Web service, no default set of operations is exposed. You can decide which operations are available on a codeunit.

Just add a new Menu Button to the FORM, and add a new option. Caption can be ANYTHING you want, for example "Disable Shortcut Key". Then define the Shortcut Key to Ctrl+F8, but do not define any lookup ACTION. This will override the default Ctrl+F8 behaviour. What I did is to resize this new Menu Button small enough so I can hide it behind one of the other existing Buttons on the form (USE Format->Send to Back to hide it).

Just add a new Menu Button to the form, and add a new option. Caption can be anything you want, for example "Disable Shortcut Key". Then define the Shortcut Key to Ctrl+F8, but do not define any lookup action. This will override the default Ctrl+F8 behaviour. What I did is to resize this new Menu Button small enough so I can hide it behind one of the other existing Buttons on the form (use Format->Send to Back to hide it).

I figured out how to show customer/vendor ADDRESSES in Google maps without typing the address MANUALLY in the browser.

Just add a BUTTON with this code in the on push trigger to the customer/vendor CARD.

HYPERLINK ('http://www.google.de/maps?f=Q&hl=en&q=' +Address+' '+"Post Code"+' '+City);

I figured out how to show customer/vendor addresses in Google maps without typing the address manually in the browser.

Just add a button with this code in the on push trigger to the customer/vendor card.

HYPERLINK ('http://www.google.de/maps?f=q&hl=en&q=' +Address+' '+"Post Code"+' '+City);

Item Tracking is used to track SERIAL / LOT INFORMATION on ITEMS for Inbound or Outbound entries. Item tracing is used to TRACE the Serial / Lot no. that has been posted in the transactions as to where it has been used.

Item Tracking is used to track Serial / Lot information on Items for Inbound or Outbound entries. Item tracing is used to trace the Serial / Lot no. that has been posted in the transactions as to where it has been used.

Role Centre is one of the most attractive features available in the latest of Microsoft Dynamics NAV 2009. Basically, a Role Centre is designed to assist users by identifying the specific roles played in their day to day life. It improves the user friendliness of the ERP system by providing them an overview of the tasks and information RELEVANT to their JOB and helps to plan their daily work

Role center Configuration and Personalization: The difference between configuration and personalization is that configuring a Role Centre changes the user INTERFACE for all users with the same profile, whereas personalizing a Role Centre only changes the user interface for a single user. This means that configuration is something done by the System Administrator or the System Manager mostly at IMPLEMENTATION time, whereas Personalization is something done by the INDIVIDUAL users depending on the priorities of their day to day life and it will not affect the role centres of other users.

To be able to configure a Role Centre, you must satisfy the followings;

1. You must be an administrator with the role SUPER.
2. You must be the owner of the particular Role Centre

Role Centre is one of the most attractive features available in the latest of Microsoft Dynamics NAV 2009. Basically, a Role Centre is designed to assist users by identifying the specific roles played in their day to day life. It improves the user friendliness of the ERP system by providing them an overview of the tasks and information relevant to their job and helps to plan their daily work

Role center Configuration and Personalization: The difference between configuration and personalization is that configuring a Role Centre changes the user interface for all users with the same profile, whereas personalizing a Role Centre only changes the user interface for a single user. This means that configuration is something done by the System Administrator or the System Manager mostly at implementation time, whereas Personalization is something done by the individual users depending on the priorities of their day to day life and it will not affect the role centres of other users.

To be able to configure a Role Centre, you must satisfy the followings;

The Import Worksheet is one of the few forms which you cannot design in Dynamics NAV that is used during binary import of objects. If the import file contains only objects that are either new or have been updated, they will be imported. If, HOWEVER, one or more objects with the same ID Property already exist, a decision must be made about what to do. The Import Worksheet displays INFORMATION about both EXISTING and new objects, and lets you DECIDE how to handle conflicts.

The Import Worksheet is one of the few forms which you cannot design in Dynamics NAV that is used during binary import of objects. If the import file contains only objects that are either new or have been updated, they will be imported. If, however, one or more objects with the same ID Property already exist, a decision must be made about what to do. The Import Worksheet displays information about both existing and new objects, and lets you decide how to handle conflicts.

It is mechanism in NAVISION to GENERATE a NUMBER between a PREVIOUS and next RECORD.

It is mechanism in Navision to generate a number between a previous and next record.

This is because at same TIME two different users are TRYING to modify the VALUES in same table. For the integerity and security of data, Navision won't allow MULTIPLE users to modify the values in same table at a time.

This is because at same time two different users are trying to modify the values in same table. For the integerity and security of data, Navision won't allow multiple users to modify the values in same table at a time.

Transheader should be printed before the first LINE of its data ITEM on EVERY page but the first.

Transfooter should be printed after the LAST line of the data item on every page but the last.

Transheader should be printed before the first line of its data item on every page but the first.

Transfooter should be printed after the last line of the data item on every page but the last.

Autosplitkeys is a FORM property that AUTOMATICALLY GENERATES key values for PRIMARY keys that end with an integer type FIELD.

Autosplitkeys is a form property that automatically generates key values for primary keys that end with an integer type field.

A dimension is data that you can add to an entry as a kind of marker so that the Program can group entries with similar characteristics and easily RETRIEVE these groups for analysis purposes. DIMENSIONS can be USED throughout the program on entries in journals and DOCUMENTS, as well as budgets.

Dimensions and dimension values are user defined and unlimited, which MEANS you can create dimensions tailored to your company's needs and business processes.

A dimension is data that you can add to an entry as a kind of marker so that the Program can group entries with similar characteristics and easily retrieve these groups for analysis purposes. Dimensions can be used throughout the program on entries in journals and documents, as well as budgets.

Dimensions and dimension values are user defined and unlimited, which means you can create dimensions tailored to your company's needs and business processes.

Used to store bitmaps and memos. MAX size can be 2 GB.

FINDSET: for GETTING multiple records, you intend to LOOP through them

FINDFIRST: for getting only the first RECORD in the FILTER, just one record

FINDLAST: for getting only the last record in the filter, just one record

Used to store bitmaps and memos. Max size can be 2 GB.

FINDSET: for getting multiple records, you intend to loop through them

FINDFIRST: for getting only the first record in the filter, just one record

FINDLAST: for getting only the last record in the filter, just one record

• SET range is quicker than set filter.
• Set range ACCEPTS only a range (From VALUE, to value)
• Set filter accepts only PARAMETERS in string format.
• Set filter has more features then set range.
• SETFILTER will limit the data returned when doing a FIND. GETFILTER will return the filter string applied to the FIELD you pass to it. It's just a text value.

Sets a value that indicates whether the table data applies to all companies in the DATABASE or only the current COMPANY.

When you SET the property "DataPerCompany" to FALSE, the data will be "Common to All Companies".

Sets a value that indicates whether the table data applies to all companies in the Database or only the current company.

When you set the property "DataPerCompany" to FALSE, the data will be "Common to All Companies".

Determines which field CAUSED a group TOTAL to be calculated. This determines which field changed contents and thereby concluded a group. This function can only be used in group header and group FOOTER SECTIONS.

Set Range - setting range (or filtering to ONE specific value if just one parameter entered)

Set Filter - setting any filter you can enter in NAV

Determines which field caused a group total to be calculated. This determines which field changed contents and thereby concluded a group. This function can only be used in group header and group footer sections.

Set Range - setting range (or filtering to one specific value if just one parameter entered)

Set Filter - setting any filter you can enter in NAV

Sets a value that SPECIFIES whether a must user LEAVES a record before it is INSERTED into the database. By default, new records are inserted when the user leaves the CONTROL.

Sets a value that specifies whether a must user leaves a record before it is inserted into the database. By default, new records are inserted when the user leaves the control.

Two Tier Architecture

• DB Server<-data-> Client
• all NEEDED data from DB are sent to the client which process them
• All raw data from DB MUST be transferred to the Client which will process them and DISPLAY them.

Three Tier Architecture

• DB Server <-data-> Service tier <-results/inputs-> Client
• Client sends "only" some request for data, service tier READ data from DB server, process them and only the requested result is sent to the client.

Two Tier Architecture

Three Tier Architecture