Skip to main content

Posts

Showing posts from May, 2012

How to use Switch case in MSD axapta

How to use Switch case in axapta The switch statement evaluates the variable used in the statement and instantly knows which case to continue to, as opposed to the if else if that has to evaluate from top to bottom until the if statement returns true. Notice that you have to use the break statement at the bottom of each case. If not, it will continue to execute the next case as well. The default statement can be used in a similar way as the else statement to say that if none of the other cases contained the correct value, jump to the default case instead. switch (carGroup) { case CarGroup::Economy : info("Kia Picanto"); break; case CarGroup::Compact : info("Toyota Auris"); break; case CarGroup::MidSize : info("Toyota Rav4"); break; case CarGroup::Luxury info("BMW 520"); break; default info("Standard cars"); break; }

error 23 Data error cyclic redundancy check in sql on Database

What to do if following type of error comes in eventlog during sales order posting in axapta? The operating system returned error 23(Data error (cyclic redundancy check).) to SQL Server during a read at offset 0x00001ef1832000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\axdb1.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. I tried DBCC CHECKDB but problem did not resolved Then I tried to resynchronize database and AOT but still problem exist. When I restore database then problem resolved . Is there any  other way on which we could resolve this issue. Your comments are welcome.

AIF document service through the wizard in MSDAX

AIF document service through the wizard (in AX). The service is meant for creation of a ProductionOrder. It is built on a query on the ProdTable and InventDim tables. It has ‘create’ and ‘read’ operations. The following is the screenshot of the list of classes generated and below is their descriptions: AxProdTable - The class that represents the table ProdTable AxInventDim_ProdTable - The class that represents the table InventDim AxdProductionOrder2 – Document Class ProductionOrder2 – Data Object class (the class that serializes/deserializes XML data for usage in the form of a object) ProductionOrder2Service – the service class (which has ‘create’ and ‘read’ methods apart from others) Its successfully deployed it as a web service on IIS and able to add it as a service reference in a C# application.  able to use the classes from AX (the service classes that are generated in AX on creation of the service) following necessary code in C# to call the service and make

Manage Inventory dimension in MSD axapta

Manage Inventory dimension in axapta SO what is needed to handle Inventory in Sales Lines, as e.g findorCreateDimension and other thins that were being manages in ax 2009 , using class InventDim_Ctrl InventDimCtrl_Frm etc. Axapta>>Account Receivables>>Sale Order. Create a sale Order. create sale order line. when you will create a sale order line, at the moment you select the item the system automatically checks which dimensions are needed to be filled as mandatory or not etc. the sytem finds or created inventory dimension in InventDim table. In ax 2009 the syetsm was using class InventDim_Ctrl and InventDimCtrl_Frm classes.

EP Site is not working in axapta 4.0 Error in MSDAX

EP Site is not working in ax4.0 this error Failed to establish connection. ... Microsoft.Dynamics.BusinessCon nectorNet.LogonFailedException at Microsoft.Dynamics.BusinessCon nectorNet.Axapta.Logon(BC_PROX Y_ACCOUNT_INFO* pBCProxyAccountInfo, String company, String language, String objectServer, String configuration) at Microsoft.Dynamics.BusinessCon nectorNet.Axapta.LogonUsingBCP roxyAccount(_SEC_WINNT_AUTH_ID ENTITY_W* pImpersonatedUserAccount, NetworkCredential bcProxyCredentials, String company, String language, String objectServer, String configuration) at Microsoft.Dynamics.BusinessCon nectorNet.Axapta.LogonAs(Strin g user, String domain, NetworkCredential bcProxyCredentials, String company, String language, String objectServer, String configuration) at Microsoft.Dynamics.WebParts.Se ssionItem.Init()   I got link where some suggession given link is http://msdn.microsoft.com/en-us/library/aa548699(v=ax.10).aspx Your suggession as comments are m

How to close the client session after a specific idle time in MSD Axapta

How to close the client session after a specific idle time in Axapta Go to Users form in Administration Module, select any user -> Click on User Options button. General tab under Security you will see the Automatic Shutdown field where you can put the desired number of minutes which will shutdown the session of the user if he/she is idle for the minutes entered in the former field.