a)      Using web services with SQL CLR is tedious task due to Dynamics XML Serialization assembly, which requires manual handling of second dll file.

  b)      SQL Server Agent does not pass Windows user credential.

In addition Rashed’s example used codeunit while I wanted to use page web service. Let me give the scenario:

 - A third party application is writing customer master data in non NAV database (created specifically for integration). SQL Job should then be used to periodically call the stored procedure with primary key of the table as parameter.  Stored procedure should create the record in NAV.

Here is what I did:

I did the usual things to make it work like changing the “CustomSettings” file  to have NTLM thrue

  <add key=”WebServicesUseNTLMAuthentication” value=”true”></add> 

  and restarted the NAV services.

 Then I published my webservice. I am not going to detail that as most people know how to do it. Remeber never use “localhost” in webservice link. Normal C# application works but SQL does not like it. The problem happens when you are configuring everything on 1 system (wasted 3 days to figure that out).

 Then I enabled CLR in SQL with the following script:

sp_configure ’show advanced options’, 1;

GO

RECONFIGURE;

GO

sp_configure ‘clr enabled’, 1;

GO

RECONFIGURE;

GO

Open Visual Studio (in my case VS2008 Professional Edition). Create a new SQL server project and give name “NAVSQLCLR”. A dialog will open up and ask for connection. Select the database (in my case it is NAV_Test).

Add web reference for our webservice and name it “CustomerWS”. Then Add New Item “Stored Procedure1.cs” and write your code.  Mine is as follow

using System;

using System.Data;

using System.Data.SqlClient;

using System.Data.SqlTypes;

using Microsoft.SqlServer.Server;

using System.Security;

using System.Net;

using System.Transactions;

using NAVSQLCLR.CustomerWS;

public partial class StoredProcedures

{

[Microsoft.SqlServer.Server.SqlProcedure]

public static void StoredProcedure1(int VendInt)

{

using (SqlConnection sc = new SqlConnection(”context connection = true”))

{

  try

  {

  sc.Open();

  SqlCommand sqlcomm = new SqlCommand(”SELECT

  [VendorCode],[Name],[Address] FROM

  [IntegrationDb].[dbo].[Common_Vendor] AS CV WHERE

  CV.VendorCode = ” + VendInt, sc);

  SqlDataReader dr = sqlcomm.ExecuteReader();

  while (dr.Read())

  {

  string name = dr.GetString(1);

  string addr = dr.GetString(2);

  Customer_Service custservice = new Customer_Service();

  custservice.Credentials = new

  NetworkCredential(”administrator”, “Savita1″, “ssd”);

  Customer cust = new Customer();

  cust.Name = name;

  int strlen = addr.Length;

  if (strlen <= 50)

  {

  cust.Address = addr.Substring(0, strlen);

  cust.Address_2 = “”;

  }

  if (strlen > 50 && strlen <= 100)

  {

  cust.Address = addr.Substring(0, 50);

  cust.Address_2 = addr.Substring(50, strlen - 50);

  }

  if (strlen > 100)

  {

  cust.Address = addr.Substring(0, 50);

  cust.Address_2 = addr.Substring(50, 50);

  }

  custservice.Create(ref cust);

  }

  }

  finally

  {

  sc.Close();

  }

  }

  }

  }

  Now I cannot write a hardcoded user credentials and password so I found another solution and added

WindowsImpersonationContext ctx = null;

WindowsIdentity id = SqlContext.WindowsIdentity;

ctx = id.Impersonate();

I then deployed the code. Inserted a record in common database and called the stored procedure. I ran into problem and have to change my assembly database permission level to “External Access”. Now another problem came

The assembly is authorized when either of the following is true: the database owner (DBO) has EXTERNAL ACCESS ASSEMBLY permission and the database has the TRUSTWORTHY database property on; or the assembly is signed with a certificate or an asymmetric key that has a corresponding login with EXTERNAL ACCESS ASSEMBLY permission.

I didn’t want to set database Trustworthy and looked for other solution. I signed my assembly and provided a strong name key “NAVSQLCLRkey.pfx”. Then I opened SSMS and wrote the following script.

USE master

GO

CREATE ASYMMETRIC KEY NAVSQLCLRkey FROM EXECUTABLE FILE =

 ‘C:\Users\Administrator\Desktop\NAVSQLCLR\NAVSQLCLR\bin\Debug\NAVSQLCLR.dll’

  CREATE LOGIN NAVSQLCLRLogin FROM ASYMMETRIC KEY NAVSQLCLRkey

  GRANT EXTERNAL ACCESS ASSEMBLY TO NAVSQLCLRLogin

  GO

To eliminate the need of manual handling of dll files I then created 2 file with .sql extension in notepad “postdeployscript.sql” & “predeployscript.sql” and added in my solution.

In the “predeployscript.sql” add the following code:

IF EXISTS (SELECT [name] FROM sys.assemblies WHERE [name] = N’NAVSQLCLRXML’)DROP ASSEMBLY NAVSQLCLRXML with NO DEPENDENTS;

In the “postdeployscript.sql” add the following code:

CREATE ASSEMBLY NAVSQLCLRXML from

‘C:\Users\Administrator\Desktop\NAVSQLCLR\NAVSQLCLR\bin\Debug\NAVSQLCLR.XmlSerializers.dll’

I again deployed the solution, executed the stored procedure and got the following error:

Step into: Stepping over non-user code ‘NAVSQLCLR.CustomerWS.Customer_Service.Create’

A first chance exception of type ‘System.InvalidOperationException’ occurred in System.Xml.dll

.NET Framework execution was aborted. The UDP/UDF/CLR type did not revert thread token.

The error confused me and I decided to debug it. While debugging after the exception occurred I found the real culprit

+             InnerException       {”That assembly does not allow partially trusted callers.”}       System.Exception {System.Security.SecurityException}

I modified “AssemblyInfo.cs” to include 2 lines

Using System.Security; and

[assembly: AllowPartiallyTrustedCallers].

I started again to deploy and execute and it worked.

Now the SQL Agent job. I inserted some 100 records in the common table and create the job scheduler as below

DECLARE @vendparameter int

DECLARE vendcursor CURSOR FOR

SELECT CV.VendorCode FROM IntegrationDb.DBO.Common_Vendor AS CV

OPEN vendcursor

FETCH FROM vendcursor into @vendparameter

WHILE (@@FETCH_STATUS =0)

BEGIN

EXECUTE [NAV_Test].[dbo].[StoredProcedure1] @vendparameter

FETCH NEXT FROM vendcursor into @vendparameter

END

CLOSE vendcursor

DEALLOCATE vendcursor

This is not the best code but for example I will live with it. The job didn’t run as expected and then I changed the Job owner to some user who is not “sysadmin” and SQL agent service log-on account was changed to windows login and it started working.

NAV 5.0 SP1 

a) TDS With Higher Rate :

 https://mbs.microsoft.com/partnersource/support/selfsupport/taxupdates/msd_nav5tdshighrateindia.htm?printpage=false

b) New TDS 16 A & TCS 27 D Certificates  :

 https://mbs.microsoft.com/partnersource/support/selfsupport/taxupdates/msdnav5sp1tdstcs1627_india.htm?printpage=false

c) PAN Status Change As Applicable for Vendor Details for IN Microsoft Dynamics NAV 2009 SP1

https://mbs.microsoft.com/partnersource/support/selfsupport/servicepacks/msdnav50sp1_panstatus.htm?printpage=false

d) Microsoft Dynamics NAV 5.0 SP1 Hot fix 2 

https://mbs.microsoft.com/partnersource/downloads/hotfixes/nav+5.0+sp1+hot+fix+2.htm?printpage=false

e) IN NAV 5.0 SP1 HF1 

https://mbs.microsoft.com/partnersource/downloads/hotfixes/innav50sp1hf1.htm?printpage=false

f) Platform Update 2 for Microsoft Dynamics NAV 5.0 SP1

https://mbs.microsoft.com/partnersource/support/selfsupport/hotfixes/nav500sp1update2.htm?printpage=false

NAV 2009

a) Product Download for NAV 2009

https://mbs.microsoft.com/partnersource/downloads/releases/microsoftdynamicsnav2009.htm?printpage=false

NAV 2009 SP1

a) TDS With Higher Rate

https://mbs.microsoft.com/partnersource/support/selfsupport/taxupdates/msd_nav2009tdshighrateindia.htm?printpage=false

b) New TDS 16 A & TCS 27 D Certificates

https://mbs.microsoft.com/partnersource/support/selfsupport/taxupdates/msdnav2009sp1tdstcs1627_india.htm?printpage=false

c) Tax calculation in Service Management Module

https://mbs.microsoft.com/partnersource/support/selfsupport/taxupdates/msdnav2009sp1taxation_india.htm?printpage=false

d) New TDS/TCS e-filling formats

https://mbs.microsoft.com/partnersource/support/selfsupport/taxupdates/msdnav2009sp1efiling_india.htm?printpage=false

e) Feature Pack 1

https://mbs.microsoft.com/partnersource/support/selfsupport/taxupdates/msd_nav2009sp1india.htm?printpage=false

f) PAN Status Change As Applicable for Vendor Details for IN Microsoft Dynamics NAV 2009 SP1

https://mbs.microsoft.com/partnersource/support/selfsupport/servicepacks/msdnav2009sp1_panstatus.htm?printpage=false

g) Microsoft Dynamics NAV 2009 Service Pack 1

https://mbs.microsoft.com/partnersource/downloads/releases/microsoftdynamicsnav2009sp1.htm?printpage=false

Misc.

a) Application Test Toolset for Microsoft Dynamics NAV 2009 SP1

https://mbs.microsoft.com/partnersource/deployment/resources/supplements/mdnavapplicationtest.htm?printpage=false

b) User Rights Setup for Microsoft Dynamics NAV

https://mbs.microsoft.com/partnersource/downloads/supplements/userrightsetupformicrosoftdynamicsnav.htm?printpage=false

c) Best Practices Analyzer for Microsoft Dynamics NAV 2009 SP1

https://mbs.microsoft.com/partnersource/deployment/resources/supplements/bestpracticesanalyzernav2009.htm?printpage=false

Microsoft has included some very useful fields in the 2009 i.e. RG/Service Tax Setoff Date and PLA Setoff Date.

The post assumes that you know how to post sales and purchase invoice with Excise values and also how to make payment in PLA account. In case you need me to explain the procedure, write a comment and I will include in my next blog.

Open the Bank Payment Voucher having the following fields (In case the fields are not available then insert them through Form Designer):

a)      E.C.C. No.

b)      RG/Service Tax Setoff Date

c)       PLA Setoff Date

Select the G/L account where excise payable entries have been posted. Fill the following Fields:

a)      Posting Date : Posting Date of Voucher. In this case I am taking as 05/02/11 (DD/MM/YY).

b)      RG/ServiceTax Set Off Date: Date upto which the RG credit entries and Excise Payable entries have to be taken. Normally it is the last date of the month for which settlement has to be made. In my case it will be 31/01/11 because I am making settlement for the month of Jan 2011.

c)       PLA Setoff Date : Date upto which the PLA entries have to be taken. Indian Excise law allows the company to deposit the excise amount upto 5^th of next month. So in case some PLA amount has been deposited in current month and the amount has to be used for settling the due of last month, then current date needs to be given . In my case I am taking 05/02/11.

d)      E.C.C. No. : ECC no. of location for which excise settlement has to be done. In case we have multiple excisable units then multiple entries needs to be posted. One entry will do the settlement of One Location only.

e)      Account Type : Account Type should be G/L Account.

f)       Account No. : Excise Payable account for the location.

Click on Payments Tab – Tax Payments – Excise

The following Form will be opened. This will show all the entries outstanding for settlement upto the date of RG/Service Tax Setoff Date.

Click on Apply Entries button in the bottom:

 Click in Detail Button in the bottom.  This will open the following screen

The left side of the screen shows the components, liability and remaining liability. Remaining Liability will show the unadjusted amount of duty payable.

The screen will have 3 tabs

a)      RG 23 A Part II

b)      RG 23 C Part II

c)       PLA

Each tab will show the available credit in the respective group. 

The first Row in the matrix will be “Credit Available” which will show the credit available under the component.

In case you need to use a input component for settling duty payable under other component like BED in RG 23 A part II to adjust payable under E-cess then relevant rules has to be defined in the setup under “Claim Setoff”.

Now you can fill the values in the component by using various tabs and the remaining liability should become zero for all the components (except when you have service tax credit available which you want to use for settlement).  After filling the screen should look like this:

Note that the remaining Liability has become zero for all the components. 

Now press escape which will bring you to the earlier screen with a difference:

The values of RG 23 A, RG 23 C , PLA has been filled adjacent to Excise Payable.

Again press escape and you will be come on the Bank Payment Voucher screen.  The values will be filled automatically and the voucher will seems to be out of balance

You need not modify anything but simply press post. System will automatically insert the balance account.

That will be it. We are done. You can check the posted entries.

I don’t understand why Microsoft has provided the link of Excise Settlement in the Bank Payment Voucher though the voucher never involves any Bank Account. I normally customize the Journal Voucher Form to include the option.