Microsoft Dynamics Axapta Technical,Functional Coverage

If you want to register new assembly by code in axapta then you can try following code in your programme. new SysReference(referenceName, assemblyName...).addToAOT();

There are two ways to improve performance of Import data through Excel template in axapta. Method one: You can Import the excel data into table in a dummy database of sql server or other dummy table in same database. Then you need to Create a odbc connection to the dummy database in the machine After that you need to Create a job in Axapta with odbc connectivity and pull the data by sql query. After reading the data then insert into respective tables of Axapta. You need to write database connectivity script. You can get that code on this blog too. Just use search box. Method two: Second method is you can use standard import functionality but  Don't use excel, you can use custom type importing option then convert your excel data into CSV format and define the table & columns and import the data.I am sure approx 20k records will be import few minutes.I hope This is the better way to import bulk records.

If you are facing performance issues in axapta then you can take following action. 1. Re-Indexing. 2. Create new indexes by getting hints from long query and select queries. 3. Check unwanted data in log tables and clear them if not required. 4. Increase RAM Size in sql database. 5. Check your disc where application and database installed. Required to check whether its free or not. 6. Check blocking processes from sql at working time. 7. Load balancing of AOS. I hope you get good hints from here for performance tuning.

This is probable details of Breakdown of the Microsoft Dynamics customer numbers by product. Microsoft Dynamics® CRM 39,000 companies with 3 million users  Microsoft Dynamics® AX 18,000 companies  Microsoft Dynamics® GP 43,000 companies  Microsoft Dynamics® NAV 94,000 companies  Microsoft Dynamics® SL 13,500 companies Currently CRM,AX,GP,NAV and SL are famous product of Micrsoft dynamics ERP.

How to change an Sales order from status Delivered to open order in ax 2009? In the receive now enter negative quantity and post the packing slip by selecting option receive now before posting, that's for reversing the quantity posted and making it an open order again. Edit the quantity in the order lines of already existing / posted line and the order changes to open order or create a new line in the existing order the order changes to open order. The sales order will be received if all the lines are received. If one or more lines is open the whole service order will be open.

If you are having buffer size issue while adding more fields in SalesTable. I thought to create a parallel table with SalesTable which could be used in future customization  and would associate this table on SalesTable form using SalesId relation on this new table with SalesTable. It works but only when You create new records in salesTable due to the relation defined between SalesTable and newly created table. However, it is not working with existing sales orders as there is not associated SalesId (from sales table) in newly created table. If You will go with this approach You have to run a job to update all SalesId from SalesTable to newly created table for existing records. These are other workaround rather than adding a new table or have ever come across with such requirement? 1) Insert Old Data from Orignal_SalesTable to New_SalesTable 2) Under Orignal_SalesTable, create(if not available)/see(if already) three methods, AosValidateInsert,AosValidateDelete,AOSValidateUpdate; These

Problem: Is there a way (configuration, add on or something else) to define the item coverage minimum in days instead of quantity? For example, if in the last 30 days I had 3000 Pcs in sales of an item, that means that my average sales is 100 Pcs per day. If I have now 400 Pcs on hand, that means I have 4 inventory days. Then if I could set the minimum inventory as, let say 6 days, that should mean for AX a shortage of 2 inventory days (200 Pcs that I need to purchase, therefore a planned order should be generated by master planning). Solution: The core of your requirement is not the Item coverage, what you need is to auto-generate the sales forecast based on historical sales data. Then you can use the standard functionality of item coverage code Period and define the period as your forecast bucket. In that case you make the sure that the item requirement will collect whatever in the sales forecast. I think it could work fine: The calculated forecast will need to be created in a