RE: [development-axapta] Customization Problem

Hi, Actually Ax have 2 inventdimid in transfer. InventdimId and InventdimIdto. Try to read the code of InventJourtransfer form. You will see how the InventDimId is supplied. Regards From: development-axapta@yahoogroups.com [mailto:development-axa...@yahoogroups.com] On Behalf Of Åßü

RE: [development-axapta] Re: Query extended range failure, linking InventTrans and InventDim

Hi, Try using View. Create a view for your lookup form. Don't need to trouble yourself. Then you just need to filter it out in you form. Regards From: development-axapta@yahoogroups.com [mailto:development-axa...@yahoogroups.com] On Behalf Of pkpeterson652 Sent: Tuesday, March 02, 2010

RE: [development-axapta] Can we have Serial Number in Packing Slip?

Hi, Try to do marking then after that put the total qty in the received now field. The when you are posting select in the posting combo box received now. Problem solve. Regards From: development-axapta@yahoogroups.com [mailto:development-axa...@yahoogroups.com] On Behalf Of

[development-axapta] Re: Customization Problem

Hi Abu, I did something similar a while back but found it was easier to implement by using the Barcode class. It already has logic to interpret a barcode scan and convert it to an item id and putting the code here makes it work pretty much everywhere. Below is sample code you can add to

[development-axapta] about PurchParmTable relations

Hi, I would like to figure out a relation on PurchParmTable (http://msdn.microsoft.com/en-us/library/aa864816.aspx) : PurchParmTable PurchParmTable Table PurchParmTable.ParmId == PurchParmTable.ParmId PurchParmTable.TableRefId == PurchParmTable.TableRefId there is a

RE: [development-axapta] Customization Problem

Dear i have fixed this problem it will runing successfully on client side go to step 1: InentTransferLine table in AOT step 2: then click modifiedField methood of above table step3: In this method you check these lines of case statement case fieldnum(InventTransferLine, ItemId):