The Islamic calendar or Hijri calendar is a calendar based on the cycles of the moon, used to date events in many Muslim countries and to determine the correct day on which to celebrate Islamic holy days and festivals.

A question appeared on the Navision newsgroup some years ago asking how to go about converting Gregorian to Hijri dates in Dynamics NAV, so I set about writing some code to achieve this.

I though the new year may be an appropriate time to repost that code for anyone who needs it.

You can download the Hijri Date Management codeunit here.

Example function calls:

MESSAGE(Date2Hijri(010110D,0));

This message window would show: 15/1/1431

MESSAGE(Date2Hijri(010110D,1));

This message window would show: Friday 15 Muharram 1431 A.H.

The Tracking Specification table is used in conjunction with theResrevation Entry table, Item Ledger Entry table and various temporary record handling functionality in order to attach and maintain tracking against items on document lines.

To add a new field, for example, Your Reference, you must first add this field to the Tracking Specification table and place it on screen by modifying the Item Tracking Lines form:

Reservation Entry

The new field also needs to be added to the Reservation Entry table. 

Unfortunately there is more to it than just placing the field on screen. If you try to assign a lot and fill in our new Your Reference field, close the form, then re-open, you’ll notice that the value entered has disappeared.

This is beause the new field needs to be pushed through to the Reservation Entry table.

To achieve this we need to delve into the code behind the Item Tracking Lines form.

RegisterChange

The first function we need to look at is the the RegisterChange function. 

Within this function there is a call to the CreateReservEntryFor function in the Create Reserv. Entrycodeunit. Values are passed to this function which is then used to update the reservation entries.

You can either modify the CreateReservEntryFor function and tag your field(s) on the end, or create a new function called SetCustomFields which will take your new field(s) as parameters.

The new function should look something like this:

A call to this new function must then be made from the RegisterChange function in the Item Tracking Lines form.

The new field will now be pushed through to the reservation entry table when the item tracking form is in insert mode.

It also needs to update correctly when in modify/delete mode.

EntriesAreIdentical

To do this you firstly need to modify the EntriesAreIdentical function by inserting the new Your Reference field as follows:

RegisterChange

Now we need to go back to the RegisterChange function and insert the following two lines of code which fall within ChangeType::Modify: case statement.

This code will update the reservation entries correctly when our new field Your Reference is modified.

ModifyFieldsWithinFilter

Lastly we need to add a line of code to the ModifyFieldsWithinFilter function:

The new field should now be fully operational.

In Dynamics NAV a stock take can be performed using a Physical Inventory Journal.

This journal can be automatically populated by running theCalculate Inventory function which gives a picture of what NAV “thinks” the current stock situation is.

Warehouse staff can then perform the physical stock checks in the warehouse, feed any adjustments into the journal and finally post, the negative and positive adjustments hitting the item ledger.

What if we want to easily count stock by lot/serial no. and item track the physical inventory journal?

Or want to run the Calculate Inventory function by lot no./serial no.?

Approach 1

The first method is it utilise new functionality in NAV 5.00 which allows a breakdown by lot/serial to be shown on the Phys. Inventory List report.

Warehouse staff can then use the list to record stock counts against each individual lot/serial.

Lot/serial tracked items on the journal can then be tracked using the physical counts recorded by the warehouse staff.

Users running versions prior to 5.00 should be able to port the Show Serial/Lot functionality at a reasonably low development cost.

Approach 2

Even with the ability to show Serial/lot information on the Physical Inventory List it may still be useful if you could somehow make the Calculate Inventory function lot/serial no. aware, allowing it to insert a new journal line for every item/lot/serial combination. 

The following modifications show how this can be achieved.

Inventory Journal Form

Add the Lot No. and Serial No. fields to the form:

Add a global variable of type Boolean called ByLotSerial:

Add a check box to the request form:
Set the SourceExpr to ByLotSerial
Set the caption to By Lot No./Serial No.

Report 790 – Calculate Inventory

The following changes to various functions need to be made in the Calculate Inventory report.

UpdateBuffer() Function

Change the UpdateBuffer function so that it takes two additional parameters:

• LotNo [Code 20]
• SerialNo [Code 20]

Make changes to the code as follows:

RetrieveBuffer() Function

Add two additional parameters:

• LotNo [Code 20]
• SerialNo [Code 20]

ItemBinLocationIsCalculated()

Make changes to the code as follows:

Item Ledger Entry – OnAfterGetRecord()
Make changes to the code as follows:

InsertItemJnlLine
Change the InsertItemJnlLine function so that it takes two additional parameters:

1. LotNo2 [Code 20]
2. SerialNo2 [Code 20]

        

Change the code in this functions as follows:

..

1. ..
2. ItemLedgEntry.RESET;
3. ItemLedgEntry.SETCURRENTKEY("Item No.");
4. ItemLedgEntry.SETRANGE("Item No.",ItemNo);
5. IF ItemLedgEntry.FIND('+') THEN
6.   "Last Item Ledger Entry No." := ItemLedgEntry."Entry No."
7. ELSE
8.   "Last Item Ledger Entry No." := 0;
9. // — INSERT CODE — Begin
10. IF (Quantity2 <> 0) AND ByLotSerial THEN BEGIN
11.   "Lot No." := LotNo2;
12.   "Serial No." := SerialNo2;
13. END;
14. // — INSERT CODE — End
15.  
16. INSERT(TRUE);
17. ..
18. ..

 
Change the three calls to InsertItemJnlLine found in the OnPostDataItem() trigger of the Item Ledger Entry data item:

Old code:

InsertItemJnlLine(

1.   "Item No.","Variant Code","Dimension Entry No.",
2.   "Bin Code",Quantity,PosQty);

New code:

InsertItemJnlLine(

1.   "Item No.","Variant Code","Dimension Entry No.",
2.   "Bin Code",Quantity,PosQty,"Lot No.","Serial No.");

Calculate Inventory
Running the newly modified Calculate Inventory function will produce a new journal line per item/lot no. as shown:

 

The Qty. (Phys. Inventory) field can then be completed for each line as normal.

We now need a function which will iterate through the journal lines adding the required tracking.

The ApplyTrackingLines function below shows how this may be coded, in the example, hanging from the Phys. Inventory Journal form:

ApplyTrackingLines()

1. IF NOT CONFIRM(Text67200,FALSE) THEN EXIT;
2. WITH ItemJnlLine DO BEGIN
3.   RESET;
4.   SETRANGE("Journal Template Name",Rec."Journal Template Name");
5.   SETRANGE("Journal Batch Name",Rec."Journal Batch Name");
6.   IF FIND('-') THEN BEGIN
7.     IF ReservationEntry.FIND('+') THEN
8.       EntryNo := ReservationEntry."Entry No." + 1
9.     ELSE
10.       EntryNo := 1;
11.  
12.     Window.OPEN(Text67203);
13.  
14.     REPEAT
15.       IF ("Lot No." <> '') AND (Quantity <> 0) THEN BEGIN
16.         ReservationEntry.INIT;
17.         ReservationEntry."Entry No." := EntryNo;
18.         ReservationEntry.Positive := (ItemJnlLine."Entry Type" = ItemJnlLine."Entry Type"::"Positive Adjmt.");
19.         ReservationEntry.VALIDATE("Item No.","Item No.");
20.         ReservationEntry."Location Code" := "Location Code";
21.         IF "Qty. (Phys. Inventory)" < "Qty. (Calculated)" THEN
22.           ReservationEntry.VALIDATE("Quantity (Base)",-Quantity)
23.         ELSE
24.           ReservationEntry.VALIDATE("Quantity (Base)",Quantity);
25.         ReservationEntry."Reservation Status" := ReservationEntry."Reservation Status"::Prospect;
26.         ReservationEntry."Creation Date" := WORKDATE;
27.         ReservationEntry."Source Type" := DATABASE::"Item Journal Line";
28.         ReservationEntry."Source Subtype" := "Entry Type";
29.         ReservationEntry."Source ID" := "Journal Template Name";
30.         ReservationEntry."Source Batch Name" := "Journal Batch Name";
31.         ReservationEntry."Source Ref. No." := "Line No.";
32.         ReservationEntry."Shipment Date" := WORKDATE;
33.         ReservationEntry."Qty. per Unit of Measure" := "Qty. per Unit of Measure";
34.         ReservationEntry."Lot No." := "Lot No.";
35.         ReservationEntry."Serial No." := "Serial No.";
36.         ReservationEntry.INSERT;
37.         EntryNo += 1;
38.  
39.         IF "Serial No." <> '' THEN
40.           Window.UPDATE(1,"Serial No.")
41.         ELSE
42.           Window.UPDATE(1,"Lot No.");
43.       END;
44.     UNTIL NEXT = 0;
45.   END ELSE
46.     ERROR(Text67201);
47. END;
48.  
49. MESSAGE(Text67202);

Posting
As the Lot No. and Serial No. on the item journal line are legacy fields used prior to Item Tracking, there is code within the Item Jnl.-Post Line codeunit (22) which checks these fields are blank.
We need to bypass these checks for our purposes and so allow the journal to be posted.

Change the SetupSplitJnlLine function as follows:

IF (NOT ItemJnlLine2.Correction OR IsServUndoConsumption) AND

1.   (ItemJnlLine2."Quantity (Base)" <> 0) AND
2.   ItemTrackingMgt.RetrieveItemTracking(ItemJnlLine2,TempTrackingSpecification)
3. THEN BEGIN
4.   IF DisableItemTracking THEN BEGIN
5.     IF NOT TempTrackingSpecification.ISEMPTY THEN
6.       ERROR(Text021,ItemJnlLine2.FIELDCAPTION("Operation No."),ItemJnlLine2."Operation No.");
7.   END ELSE BEGIN
8.     IF TempTrackingSpecification.ISEMPTY THEN
9.       ERROR(Text100);
10.     IF NOT ItemJnlLine2."Phys. Inventory" THEN BEGIN // — INSERT LINE ++
11.       ItemJnlLine2.TESTFIELD(ItemJnlLine2."Serial No.",'');
12.       ItemJnlLine2.TESTFIELD(ItemJnlLine2."Lot No.",'');
13.     END;                                             // — INSERT LINE ++
14.     ItemJnlLine2.TESTFIELD(ItemJnlLine2."New Serial No.",'');
15.     ItemJnlLine2.TESTFIELD(ItemJnlLine2."New Lot No.",'');

Microsoft have now started to remedy this situation to a certain degree.

Look at the Sales Shipment report (208) in a Cronus database. Sitting at the bottom of the Options tab is a check box called Show Serial/Lot No. Appendix. Ticking this option will print an appendix page giving a breakdown of the lot/serial information associated with the shipment.

The appendix page hasn’t been applied to all appropriate reports though, so it still leaves some work for us to do…

The following example shows how you can add the appendix page to to any Document type report, using the Purchase Receipt Report (408) to illustrate.

For this purpose we’ll define a variable which points to the Microsoft XML automation server and the XMLHTTP class:

'Microsoft XML, v6.0'.XMLHTTP

The C/AL required will be as follows:

Create the Automation object:

Define the reqest:

Send the request:

Process the response:

In the simplified example above, the ASP page called search.asp is responsible for generating the response.

The XML automation server will pass a request to this page then retrieve a response via theresponseText which can then be processed as required.

This articles demonstartes how to access and use CuteFTP’s transfer engine from within Microsoft Dynamics NAV to upload, rename and delete files on a remote ftp server. It’s slighlty more refined than the somewhat Heath Robinson approach required to use the in built windows ftp client described in an earlier article.

To follow the examples you’ll need to install either CuteFTP Home or CuteFTP Professional, both of which are available for download from the GlobalSCAPE website as 30-day trial versions.

We’ll place all the required functions in a new codeunit called FTPManagement which can then be called as and when required.

The first step after creating the new codeunit is to add a reference to the CuteFTP COM interface by defining a global variable of type Automation with a subtype of 'CuteFTPPro 8.0 Type Library'.TEConnection.

The SetHost function

This function sets the hostname and logon credentials. These are passed in via three parameters,NewHostname, NewLogin, NewPassword. 

The second line, Hostname := NewHostname; assigns the NewHostname parameter to a global variable called Hostname so we can reference it outside the scope of this function for error messages.

The third line, CuteFTP.Option('ThrowError',0); is included so that we can trap and handle any errors from within NAV.

The UploadFile function

This function uploads a local file to a remote ftp host and takes two parameters, LocalFilename and RemoteFilename.

An error will be thrown if the local file cannot be found. The text constant for the error, Text001 should read: Unable to find local file ‘%1′.

The DeleteFile function

The RenameFile function

This function renames a remote file specified in the FromFilename paramter to the name specified in the ToFilename paramter.

An error will be thrown if the remote file cannot be found.

The Close function

This function disconnects from the host.

Calling the functions

Function calls to the FTPManagement codeunit can now be made as follows: 

To upload a file:
FTPManagement.SetHost('ftp.example.com','username','password');
FTPManagement.UploadFile('c:\localfilename.txt','remotefilename.txt');

To delete a remote file:
FTPManagement.SetHost('ftp.example.com','username','password');
FTPManagement.DeleteFile('test.txt');

To rename a remote file:
FTPManagement.SetHost('ftp.example.com','username','password');
FTPManagement.RenameFile('oldfilename.txt','newfilename.txt');

The codeunit can be expanded to include download functionality, upload folders with multiple files etc.

For further information on the transfer engine download the user guide which includes a chapter on the SDK.

1. Make sure the ALL security role has Read permissions to Table Data 2000000003 Member Of
2. Create a new Role to control access to the field(s). In this example I’m going to control access to the Unit Price field on the Item, so i’ve created a role called ITEM-UNITPRICE.
3. Create a new Codeunit called FieldLevelSecurityManagement and a function calledCheckFieldPermission
4. In the table where the field(s) to be controlled are located, create a global variable calledFieldLevelSecurityManagement which points to the FieldLevelSecurityManagement codeunit created above.

Now any user which hasn’t been granted specific permission to the Unit Price field will receive an error if they attempt to modify it.

fig 1.

http://localhost:8888/nextequalzero/?p=65
		
			Codeunit 416 Datetime Mgt. which contained functions to handle conversions to and from Date-Time type fields has been removed.

The inbuilt C/AL functions of CREATETIME, DT2TIME and DT2DATE should now be used instead.
These functions have been around for some time but with the NAV 5.0 release MS have streamlined the codebase by removing this codeunit and changing the references to it.
Any bespoke code which references this defunct codeunit will also need to be changed.
Examples:
Old code: "Starting Date-Time" := DatetimeMgt.Datetime("Starting Date","Starting Time")
New code: "Starting Date-Time" := CREATEDATETIME("Starting Date","Starting Time");
 

Old code: DatetimeMgt.Datetime2Time("Starting Date-Time");
New code: DT2TIME("Starting Date-Time");
 
Old code: DatetimeMgt.Datetime2Date("Starting Date-Time");
New code: DT2DATE("Starting Date-Time");
]]>
			http://www.nextequalzero.com/2007/06/codeunit-416-datetime-mgt-removed-in-dynamics-nav-50/feed/
		0
		
		
		
		http://www.nextequalzero.com/2007/06/unattended-ftp-upload-from-dynamics-nav/
		http://www.nextequalzero.com/2007/06/unattended-ftp-upload-from-dynamics-nav/#comments
		Sat, 02 Jun 2007 19:39:55 +0000
		Ian Crocker
				
		
		
		
		

		http://localhost:8888/nextequalzero/?p=70
		
			There are a number of ways in which an FTP upload can be achieved in Dynamics NAV.

This article focuses on a neat way of utilising the in-built Windows FTP client.
It is achieved by generating a batch file from within NAV which is then launched and in turn writes an unattended script file which is then passed to the ftp command using the -s switch. All files are written on the fly in the temporary folder on the local machine and are gracefully cleaned up afterwards.

The full piece of code looks like this:



// Get handle on a temporary filename


//


TextFile.CREATETEMPFILE;


Filename := TextFile.NAME + '.bat';


TextFile.CLOSE;


 


// Create the file and set textmode ready for writing


//


TextFile.CREATE(Filename);


TextFile.TEXTMODE(TRUE);


 


// Write the batch file and then close


//


TextFile.WRITE('@ECHO OFF');


TextFile.WRITE('> script.ftp ECHO open ftp.hostname.com');


TextFile.WRITE('>>script.ftp ECHO USER username');


TextFile.WRITE('>>script.ftp ECHO password');


TextFile.WRITE('>>script.ftp ECHO Send c:\file.txt');


TextFile.WRITE('>>script.ftp ECHO Bye');


TextFile.WRITE('FTP -s:script.ftp -n ftp.hostname.com');


TextFile.WRITE('TYPE NUL >script.ftp');


TextFile.WRITE('DEL script.ftp');


TextFile.WRITE(':retry_del');


TextFile.WRITE('DEL "' + Filename + '" > NUL');


TextFile.WRITE('if exist "' + Filename + '" goto retry_del');


TextFile.CLOSE;


 


// Launch the batch file


//


NAVShell('"' + Filename + '"');






NAVShell(CommandLine : Text[1024])


CREATE(WshShell);


WshShell.Run(CommandLine);


CLEAR(WshShell);



First thing to notice is that I’ve hard-coded the connection and filename details which are written out to the batch file. This is simply for illustrative purposes. In a production environment they would probably be pulled from a Setup table.
Also, the batch file is not launched using the SHELL command as might be expected. Instead a function which invokes the Windows Script Host Object Model is used. This is to prevent the warning messages which appear in Dynamics NAV when attempting to launch an executable or batch file from the command line for the first time. And as the batch file will have a different name each time the code is triggered, we want to stop this dialog popping up.
You can read more about the NAVShell function itself here
The batch file when generated by NAV will look something like this:
@ECHO OFF

> script.ftp ECHO open ftp.hostname.com

>>script.ftp ECHO USER username

>>script.ftp ECHO password

>>script.ftp ECHO Send c:\file.txt

>>script.ftp ECHO Bye

FTP -s:script.ftp -n ftp.hostname.com

TYPE NUL >script.ftp

DEL script.ftp

:retry_del

DEL "C:\Documents and Settings\[username]\Local Settings\Temp\__TEMP__.O@3.bat" > NUL

if exist "C:\Documents and Settings\[username]\Local Settings\Temp\__TEMP__.O@3.bat" goto retry_del
When launched, the batch performs the following tasks:

Generates an unattended script file on the fly
Launches the ftp command passing in the script file with the -s switch
Deletes the script file (script.ftp)
Deletes itself (the .bat file)


As usernames and passwords are stored in the clear in the script.ftp and batch files, both are deleted when the ftp process has completed.
The above example uploads one file to the ftp host address. It can however be adapted to work for both uploads and downloads, and to handle multiple file transfers if required. This is simply a case of adding the required ftp functions to the batch file which is written by NAV.

]]>
			http://www.nextequalzero.com/2007/06/unattended-ftp-upload-from-dynamics-nav/feed/
		1
		
		
		
		http://www.nextequalzero.com/2007/06/how-to-use-windows-script-host-object-model-instead-of-shell/
		http://www.nextequalzero.com/2007/06/how-to-use-windows-script-host-object-model-instead-of-shell/#comments
		Sat, 02 Jun 2007 08:43:24 +0000
		Ian Crocker
				
		

		http://localhost:8888/nextequalzero/?p=75
		
			Sometimes the SHELL command in Dynamics NAV doesn’t always work as we would like in every situation.

In such a case the Windows Script Host Object Model and it’s WshShell class may be an alternative method of running command line statements.
To build the function:

Create a function called NAVShell which takes a Text parameter of 1024. This will be used to pass in the command line.
Create a local variable called WshShell with a type of Automation and Subtype of ‘Windows Script Host Object Model’.WshShell

Enter the following code in the new function:

NAVShell(CommandLine : Text[1024])
CREATE(WshShell);
WshShell.Run(CommandLine);
CLEAR(WshShell);

We can now call the function as in the following example which launches notepad:
NAVShell(‘notepad.exe’);
]]>
			http://www.nextequalzero.com/2007/06/how-to-use-windows-script-host-object-model-instead-of-shell/feed/
		0