1
Unexpected behavior of the Find function on Sales/Purchase document line.
Follow the repro steps to understand the issue:
1.Take a NAV2017 CZ database with the last CU implemented
2. Create a new Sales Invoice
HEADER: Customer No. = 10000
3 Create a new document line
a) Type = G/L Account
b) No. = insert account with number 602120
c) Change the Description in the row to "Reklama". Confirm
================================================
ACTUAL RESULTS
- Because there is an account named "Reklama" in the list of G/L Accounts,
the system automatically changes (without warning) the account number in the document line (inserts the searched account).
================================================
EXPECTED RESULTS
- If the account number is already entered in the line, then no longer looking for another account when changing the description.
Or use a warning, similar as in the case when line type is = Item:
"We found an item with the description "XXX" (No. 70100).
Did you mean to change the current item to 70100?"
Follow the repro steps to understand the issue:
1.Take a NAV2017 CZ database with the last CU implemented
2. Create a new Sales Invoice
HEADER: Customer No. = 10000
3 Create a new document line
a) Type = G/L Account
b) No. = insert account with number 602120
c) Change the Description in the row to "Reklama". Confirm
================================================
ACTUAL RESULTS
- Because there is an account named "Reklama" in the list of G/L Accounts,
the system automatically changes (without warning) the account number in the document line (inserts the searched account).
================================================
EXPECTED RESULTS
- If the account number is already entered in the line, then no longer looking for another account when changing the description.
Or use a warning, similar as in the case when line type is = Item:
"We found an item with the description "XXX" (No. 70100).
Did you mean to change the current item to 70100?"
STATUS DETAILS
Declined
Ivan Koletic (administrator)
Thank you for reaching out. Your suggestion seems to be a product bug. Please reach out to the relevant support channels as specified in Product Support
Sincerely,
Ivan Koletic
PM, Microsoft