Method Community

 

Issue with custom field saving in Item Receipt Line Items

Last post 11-01-2011 11:35 AM by mlepitt. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 10-18-2011 10:34 AM

    Issue with custom field saving in Item Receipt Line Items

    I am having an issue with a custom field saving in Item Receipt Line Items.  I go to the item receipt, enter the required information, select a PO and pull the line items from the PO.  The PO may have serial numbers already entered in them as Quickbooks "Other1" for the line.  If so, it carries it over to the Item Receipt.  I save the Item receipt and go to another receipt, when I go back the serial numbers are gone.  Also, if I happened to enter my own serial number that did NOT carry over from the PO, it looses that also.  If after moving away from the receipt and then coming back, I add the serial numbers, it then finally takes.  I can understand some oddness on the screen when editing, but when you create the item receipt and link it to a PO, the line items are inserted directly into the table, not a temporary value on the screen.  Please advise what things I should be looking at to resolve this issue.

  • 10-18-2011 2:48 PM In reply to

    Re: Issue with custom field saving in Item Receipt Line Items

    mlepitt-

    We are aware of the cause of this issue and are working on addressing it. I will update this forum post once its resolved.

    -Michael

    Michael Melo
    Product Manager
    Method Integration Inc.
    Website: http://www.method.me
    LinkedIn: http://www.linkedin.com/in/MichaelMelo
  • 10-19-2011 8:55 AM In reply to

    Re: Issue with custom field saving in Item Receipt Line Items

    Answer

    mlepitt-

    This issue should now be resolved. Smile

    -Michael

    Michael Melo
    Product Manager
    Method Integration Inc.
    Website: http://www.method.me
    LinkedIn: http://www.linkedin.com/in/MichaelMelo
  • 11-01-2011 11:35 AM In reply to

    Re: Issue with custom field saving in Item Receipt Line Items

    Yes, this issue was resolved when you alerted us of the fix.  Thank you!

Page 1 of 1 (4 items)