D365 Finance & Operations and Dynamics AX Forum

UPDATE SALESLINE
SET SALESSTATUS = 3    -- 3=Invoiced
WHERE SALESID = '12345678SO'
AND LINENUM = 1.00000

​Maybe this will work for AX 2012 RTM too.

UPDATE SALESLINE
SET SALESSTATUS = 3    -- 3=Invoiced
WHERE SALESID = '12345678SO'
AND LINENUM = 1.00000

​Maybe this will work for AX 2012 RTM too.

UPDATE SALESLINE
SET SALESSTATUS = 3    -- 3=Invoiced
WHERE SALESID = '12345678SO'
AND LINENUM = 1.00000

​Maybe this will work for AX 2012 RTM too.

Rudy,

SalesLine.LineNum and PurchLine.LineNum ARE NOT UNIQUE within an order.

Given a large enough order and enough edits, you will find duplicated line numbers.  Depending on whether the user uses a down arrow or control-n to add lines, they can create line 1.0, then 0.5, 0.25, 0.12, 0.06, 0.03, 0.02, 0.01, 0.01, 0.01, etc.  It's rare, but it will happen sooner or later.

You should be keying off LotID (InventTransID) as it is kept unique for the table by index.

Never use LineNum in a where clause: been there, got burned, still have the scars 8^)

UPDATE SALESLINE
SET SALESSTATUS = 3    -- 3=Invoiced
WHERE SALESID = '12345678SO'
AND LINENUM = 1.00000

​Maybe this will work for AX 2012 RTM too.

Rudy,

SalesLine.LineNum and PurchLine.LineNum ARE NOT UNIQUE within an order.

Given a large enough order and enough edits, you will find duplicated line numbers.  Depending on whether the user uses a down arrow or control-n to add lines, they can create line 1.0, then 0.5, 0.25, 0.12, 0.06, 0.03, 0.02, 0.01, 0.01, 0.01, etc.  It's rare, but it will happen sooner or later.

You should be keying off LotID (InventTransID) as it is kept unique for the table by index.

Never use LineNum in a where clause: been there, got burned, still have the scars 8^)

UPDATE SALESLINE
SET SALESSTATUS = 3    -- 3=Invoiced
WHERE SALESID = '12345678SO'
AND LINENUM = 1.00000

​Maybe this will work for AX 2012 RTM too.

Rudy,

SalesLine.LineNum and PurchLine.LineNum ARE NOT UNIQUE within an order.

Given a large enough order and enough edits, you will find duplicated line numbers.  Depending on whether the user uses a down arrow or control-n to add lines, they can create line 1.0, then 0.5, 0.25, 0.12, 0.06, 0.03, 0.02, 0.01, 0.01, 0.01, etc.  It's rare, but it will happen sooner or later.

You should be keying off LotID (InventTransID) as it is kept unique for the table by index.

Never use LineNum in a where clause: been there, got burned, still have the scars 8^)

UPDATE SALESLINE
SET SALESSTATUS = 3    -- 3=Invoiced
WHERE SALESID = '12345678SO'
AND LINENUM = 1.00000

​Maybe this will work for AX 2012 RTM too.

I've seen same problem and find that using the Cancel Deliver remainder fixes the orphaned invent trans record. Suggest trying this first.

Also, I would suggest using an AOT job when manipulating records to ensure that AX logic is employed. Deleting an InventTrans record in SQL will not flow the corrected values in InventSum, for example.  

Rudy,

SalesLine.LineNum and PurchLine.LineNum ARE NOT UNIQUE within an order.

Given a large enough order and enough edits, you will find duplicated line numbers.  Depending on whether the user uses a down arrow or control-n to add lines, they can create line 1.0, then 0.5, 0.25, 0.12, 0.06, 0.03, 0.02, 0.01, 0.01, 0.01, etc.  It's rare, but it will happen sooner or later.

You should be keying off LotID (InventTransID) as it is kept unique for the table by index.

Never use LineNum in a where clause: been there, got burned, still have the scars 8^)

UPDATE SALESLINE
SET SALESSTATUS = 3    -- 3=Invoiced
WHERE SALESID = '12345678SO'
AND LINENUM = 1.00000

​Maybe this will work for AX 2012 RTM too.