Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Visibility of PKs in app somewhere #627

Open
timmyhadwen opened this issue Mar 18, 2025 · 5 comments
Open

Visibility of PKs in app somewhere #627

timmyhadwen opened this issue Mar 18, 2025 · 5 comments

Comments

@timmyhadwen
Copy link

We use the PKs as IDs for a lot of our process including part IDs and lot IDs (stock items) as an easy way to be able to yell out to other people in the office, as well as an easy way to find a specific bag of components by the ID rather than having to scan them all.

Currently there is no way to see this in the app and therefore we end up back on the computer to dig out which part is which.

As this isn't everyones use case, I propose we add a line to parts and stock items which is the PK field, similar to the current last updated, status, notes etc.

@SchrodingersGat
Copy link
Member

I like the idea of adding in PK values. I would suggest that we add it to all models types, not just parts / stock items? Perhaps it could be disabled / hidden with a user setting.

Would you like to submit a PR for this?

@timmyhadwen
Copy link
Author

Yep that makes sense. I'll get the other issues sorted first then come back for this one if it hasn't been touched in the meantime

@timmyhadwen
Copy link
Author

@SchrodingersGat Been having a look at doing this and the others today, seems simple enough however it would seem the stock item detail is architected differently to the part detail, meaning the part detail scrolls fine, but the stock item detail does not. Only noticed this after adding the PK field and now cannot see the notes field off the bottom of the screen...

Any ideas?

@SchrodingersGat
Copy link
Member

Hmm good point, I had not noticed that. There may be a difference in the way that the two widgets are being constructed

@timmyhadwen
Copy link
Author

Cool I'll see what I can dig out, it seems similar screens work fine and it's limited to just this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants