-
Notifications
You must be signed in to change notification settings - Fork 23
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
🐞[BUG] After synchronization supplier part turns into own part #1271
Comments
I took a closer look to the issue:
Since there is no relationship object in the reponse, I'll guess that we map this automatically as an OWN part. We should either block the synchronization of Supplier/Customer parts or find out the corresponding OWN Part and synch that instead. |
Description
On E2E-A I synchronized a supplier part. Afterwards it turned into an own part.
Now the part has two owners.
Current behaviour
On E2E-A I synchronized the part urn:uuid:f11ddc62-3bd5-468f-b7b0-110fe13ed0cd which was shown as supplier part before but is now an own part:
On E2E-B the part is still shown as own part:
Expected behavior
It should not be possible for a part to have two owners. After synchronization I would expect the owner to stay the same.
One assumption is that the part is duplicated in the IRS (one as own part, one as supplier part) and after synchronization one of them is randomly selected (based on which one was first fetched?).
Steps to reproduce the Bug
This may not always work (depending on which owner is shown in the first place and how the process works)
Root cause: #1271 (comment)
The issue appears when trying to sync a traversal aspect (singleLevelBomAsBuilt) or similiar directly with irs instead of doing a registry reload.
The text was updated successfully, but these errors were encountered: