Physical Count Adjustment not updating YORN attributes correctly

Body

A new YORN type attribute was added to the INVTRANS Object to help identify whether a physical count update was entered as part of a "High Value Cycle Count" or a "Regular Cycle Count".  The updated YORN attribute value is not saved to the correct transaction record which is not allowing us to identify what type of cycle count caught the physical count discrepancy. 

 
1. Open Database Configuration and add a new YORN type attribute to INVTRANS Object. 
2. Save Record. 
3. Start Admin Mode, Apply Configuration Changes and stop Admin Mode. 
4. Open INVENTOR Application in the Application Designer. 
5. Open Edit Dialogs box and select PHYSCNTADJ. 
6. Add new Table Column to the already existing section. 
7. Open Properties box for new Table Column. 
8. Select new YORN attribute in the Attribute box and use fully qualified name (INVTRANS.AttributeName]) to define the attribute property. 
9. Save. 
10. Go to Inventory, select an item and select the Select Action>Inventory Adjustments>Physical Count. 
11. Update the physical count and check the box of the new YORN attribute.  Click OK. 
12. On a SQL Tool, run a query against the INVTRANS Table for the Item and Storeroom combination used in the physical count update.  The query results will show the new physical count update transaction but the new YORN attribute value for the new transaction will show as 0 (zero). 
 

In the described scenario, one insert statement and one update statement are generated before a save is performed. 
 
The update statement is intended by you to update the record created by the previous insert statement.  However, because this record does not yet exist in the database, an incorrect INVTRANSID is used for the update statement. 
 
The test case adds an attribute to invtrans object. Adjust Physical Count action takes values from INVBALANCES object ( where the user added a YORN  attribute to  INVTRANS ). 
 
When the invtrans record is inserted, the YORN field has a default value 0. The relationship from INVBALANCES to INVTRANS picks up the first record in Invtrans and updates that YORN attribute. 
 
A possible solution would be to add the YORN attribute to INVBALANCES in addition to INVTRANS  and then override the java code or create a crossoover domain. 

See ya