It is no longer possible to use a custom text on a sales line if another account exist with same name about alappextensions HOT 10 CLOSED

I would make it a configuration setting. The general rule should be if "No". contains a real item, the text-based search should be disabled. I can only imagine bad things to happen from the current behaviour. It should be possible to disable this application-wide as well, though.

from alappextensions.

I agree, It screwed two of my invoices up already because it changed account numbers without me noticing it.
So I disabled the functionality in table 37 (naughty boy :))

from alappextensions.

Lets just guess, it is also there in T39 and T5902?

from alappextensions.

T39 yes but not T5902

from alappextensions.

How consistent ;)

from alappextensions.

When was the last time changes were made to the Service module? :)

from alappextensions.

T5902: 2018 CU 06, refactored line discount % calculation ;)

from alappextensions.

An answer would be this feature- request: OnAfterInput- Trigger
Implement search as OnAfterInput- Trigger of the "No."- Field as we could do it in former NAV- Classic Client. It's also easier to unterstand by the users to enter item- search via "No." than switch to Description.

from alappextensions.

The team has added this to their backlog and will get back to it later.
Thanks for providing feedback.

from alappextensions.

Solved in April 19 Business Central release: https://docs.microsoft.com/en-us/business-applications-release-notes/April19/dynamics365-business-central/application-enhancements#control-item-creation-from-lookups-on-documents

from alappextensions.