Issue with counting stock for certain parts in InvenTree

[palagap]

Hi there,

We noticed an counting parts issue that affects some of the parts we have loaded into InvenTree, but not others. For example, when we try to count the stock of this part, it looks like the following:

Clicking on the “Count part stock” option results in this blank display:

On the other hand, for another part, we see the following:

Clicking on the “Count part stock” option now results in the following, as expected:

Most parts seem to have no issue with the count part stock option, but a few do. We compared part settings between the parts that don’t have this issue and those that do, and could not find any differences. Do you have any suggestions on how to resolve this problem? We are running the latest stable version of InvenTree.

The InvenTree demo seems to also have the same issue for some parts:

Clicking on “Count part stock”:

[SchrodingersGat]

@palagap you might see this message if all the stock item objects you have selected are "serialized" - these can't be "counted". Is this the case maybe?

[palagap]

Unfortunately that's not the case - we verified that the parts that are presenting a problem do not have serial numbers. Some of the parts in the InvenTree demo that have this issue are:

https://demo.inventree.org/part/77/#
https://demo.inventree.org/part/81/#
https://demo.inventree.org/part/88/#

[SchrodingersGat]

I had a look at the parts you listed, and all the available stock is actually serialized (see below):

There should certainly be a better information message for the user here, but this lines up with my comments above - serialized stock items cannot be "counted"

[palagap]

Yes, you're right - the ones from the demo are serialized, but the ones in our system are not and still have the issue. Here's what it looks like from our end:

[SchrodingersGat]

Can you reproduce this with any parts on the demo server which have non-serialized stock items?

[palagap]

Unfortunately we can't replicate this on the demo server; it just seems to be an issue on our end. We're going to try duplicating the part and making the old one inactive; hopefully that fixes the issue.