Replies: 4 comments 2 replies
-
@gunstr that's strange, certainly not intended behavior. Can you please provide some screenshots or other examples of this? BTW the demo site is up again, perhaps you can try to reproduce there? |
Beta Was this translation helpful? Give feedback.
-
@SchrodingersGat Playing around with the demo site I'm getting uncertain it this is because the application has changed or if I have change work process how to create new revisions... If you duplicate the latest revision of a part, delete the old BoM and assign a new revision then the latest serial number also get duplicated I think I mostly have created new parts when adding revisions also in the past but now I'm not sure... What is the intended behavior? |
Beta Was this translation helpful? Give feedback.
-
@gunstr can you provide some screenshots of the issue? |
Beta Was this translation helpful? Give feedback.
-
@SchrodingersGat I'm not sure exactly what you need but I reproduced the issue on the Demo site and took a few screenshots... Let me know if you need more.
So far so good
This is where I think that the next serial for RevB would have been 21 in earlier releases. As I mentioned it might be so that I have created new revisions in the past by duplicating and edit the old revision. However, that method would obvioulsy fail if both revisions are manufactured in parallel why it would really be preferred that the system can create unique serials for a part across revisions. |
Beta Was this translation helpful? Give feedback.
-
In the past the next serial number has been assigned in sequence for a part across revisions. I do not know when that stopped working but now I have noticed that the serial number starts over at 1 for a new revision. Is that change intentional and is there any setting or other method to go back to the previous logic?
I cannot open the demo site right now so I have not verified the behavior there.
Beta Was this translation helpful? Give feedback.
All reactions