Skip to main content

Posts

Backdate validation for user control in EP MSD axapta

If you are seeking code for Backdate validation for user control in Enterprise portal page for  axapta then below code can help you. Its tricky to find code on EP so its helpful for you. string cDate1 = DateTime.Now.ToString("dd/MM/yyyy"); int flag = 0; Proxy.Info objinfolog = new Proxy.Info(this.AxSession.AxaptaAdapter); DateTime x; DateTime a; Int32 r1; Date1 = txtDate1.Text; Ir = dsTestNewForm.GetDataSourceView("TestNewForm").DataSetView.GetCurrent().GetRecord(); if (txtDate1.Text != "" && Ir.GetField("Date1").ToString() == "1/1/1900 12:00:00 AM") { x = DateTime.Parse(cDate1, new CultureInfo("en-CA")); a = DateTime.Parse(Date1, new CultureInfo("en-CA")); r1 = DateTime.Compare(a, x); if (Ir.GetField("Date1").ToString() == "1/1/1900 12:00:00 AM" && r1 < 0 && Date1 != "") ...

Get Current date from User control on Enterprise portal web page in Visual studio for MSD axapta

To Get Current date from User control for  Enterprise portal page in Visual studio for axapta you can set below code and show in message box. string cDate1 = DateTime.Now.ToString("dd/MM/yyyy"); Proxy.Info objinfolog = new Proxy.Info(this.AxSession.AxaptaAdapter); objinfolog.add(cDate1); You can include above code in your click event or as per your required event. This code you need to write in visual studio . You need to add particular user control in visual studio project then open code file to write the code.

The type or namespace name 'Portal' does not exist in the namespace MSD Ax 2009

Getting Error on build EP website in Visual Studio for Axapta 2009. The type or namespace name 'Portal' does not exist in the namespace 'Microsoft.Dynamics' (are you missing an assembly reference?). Solution: Solution for this error due to proxy classes required for this user control because its used in namespace. You need to take below step for the same. To fix  this error just go to your project and right click on the App_Code node in your solution explorer then select "Generate Proxies" option .  This process may take time for  building all of the classes from your proxy.  Now check again the build works for your project and its updated with your code. Proxy objects located on below folder. C:\inetpub\wwwroot\wss\VirtualDirectories\80\App_Code\Proxies

Sample code Example of Array in MSD Axapta

This is  Sample code  Example of Array in Axapta . str name; Array Arr = new Array (Types::String); int i= 1, j; Int test; TestTable TestTable; ; // Create an Str array // Write some elements in it while select TestTable { Arr.value(i, TestTable.TestTables);//(i, i*2); i++; } j = i; for (i = 1; i<j; i++) { test= Arr.value(i); while select TestTable where TestTable.TestTables == test { info(strfmt("%1", Arr.value(i))); } }

Job to import text file data to Table in MSD axapta

I want to share code to  import text file data to Table in axapta. Here is sample of one field taken in text file. #define.ioRead("r") Dialog dialog = new Dialog('File Upload'); Dialogfield dialogfield; DialogField dialogFileName; InventTable inventTable; ItemID itemID; FileIOPermission fileIOPermission; CommaTextIo io; container inLine; int lineNum; int i; ; dialogFileName = dialog.addField(typeid(FilenameSave)); dialog.run(); if(dialog.closedOk()) { fileIOPermission = new FileIOPermission(dialogFileName.value(), #ioRead); fileIOPermission.assert(); io = new CommaTextIo(dialogFileName.value(), #ioRead); if (io) { ttsbegin; while (io.status() == IO_Status::Ok) { inLine = io.read(); if (io.status() != IO_Status::Ok) { ...

Resolved - Workflow error during Order approval in MSD Axapta

Error Details:- Today I faced following error . Workflow instance:xxxxxxx was terminated for the following reason: No .NET Business Connector session could be found.. Due to this workflow work item not created after submission to workflow. Solution :To resolve this issue I did the following. 1.Compile application. 2.Resetting of IIS. 3. Reset Dotnet framework version on IIS if its changed by someone. 4. Recreate business connector configuration from Ax client configuration. This issue happen in Ax 2009 version and issue is now resolved .

Print Report in PDF in EP Site in MSD axapta 2009,4.0

If you are trying to print and display report in Enterprise portal in axapta then you need to add some code in class EPSenddocument on new method. case tablenum(CustPackingSlipJour): mailAddress = SalesTable::find(record.(fieldnum(CustPackingSlipJour,SalesId))).Email; if (record.(fieldnum(CustPackingSlipJour,InvoiceAccount))) StrVarialble1 = record.(fieldnum(CustPackingSlipJour,InvoiceAccount)); else StrVarialble1= record.(fieldnum(CustPackingSlipJour,OrderAccount)); documentTitle = fileName("SalesPKSLP"); reportName = reportstr(SalesPackingSlip); break; Here its example of sales packing slip report print . You need to add new case in switch statement.