fix: Allow creating Item as is_fixed_asset in Quick Entry. #37645
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
is_fixed_asset
currently wasn‘t included in the Quick Entry form.As the field is
set_only_once
and the doc is being saved, there‘s no way to check the box later.Effectively, it currently isn‘t possible to create a fixed asset via the Quick Entry form.
Fixing this was slightly less straightforward than expected, but in the second revision could be sufficiently solved:
is_fixed_asset
had to be added to Quick Entry.is_fixed_asset
andis_stock_item
are mutually exclusive. An informed decision in the Quick Entry form is only possible if we‘re adding the latter as well, so people can easily grasp the mutual exclusivity and choose one or the other.is_stock_item
may stay on by default, sois_fixed_asset
is initially disabled. To enableis_fixed_asset
, you first need to disableis_stock_item
. That’s halfway acceptable. However,is_stock_item
should not bounce back when disablingis_fixed_asset
again.is_fixed_asset
together with its dependent fields to the top, so it is closer tois_stock_item
. With the two mutually exclusive fields next to each other from the start, the mutual exclusivity is way easier to grasp.RPReplay_Final1698128191.mov
All in all, I think this revised approach is a clear UX improvement and a good compromise, particularly if the tests are passing, so BC is given. In a followup we may discuss whether
is_stock_item
should be on by default or not.It also fixes #37505.