Closed Zontex closed 1 year ago
@Zontex I am unable to reproduce this with a trivial example... Which version of InvenTree are you running? 3.10.4
is not a valid InvenTree version number
@SchrodingersGat Sorry my bad:
version: 0.8.0 dev commit hash: 67732f8f8 commit date: 2022-07-11
Just lowered to stable branch 0.7.4 and still see the issue, if you look at the screenshot the issue is with the table not showing from the highest price to the lowest although using the filtering function.
@Zontex looks like it is using string sorting rather than numerical (natural) sorting! Given the other major work needed on pricing, this will have to wait for next release cycle.
Describe the bug
I manually updated the component price and then went back to the BOM of the part and set to order by price (from the most expensive one to the cheapest one) but still, the position of the component was the old position even tho it's the most expensive component in the list.
Steps to Reproduce
Steps to reproduce the behavior:
Expected behavior
The most expensive component should be in first place in the list, according to the updated pricing.
Screenshots
Deployment Method
Version Information
inventree version: 3.10.4 django version: 3.2.14