You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This error happens when updating the information on a RelationReference type field.
If the user removes the value and selects a new one, the Registry creates a draft with the edited version. This draft has the correct information, but when approving the changes to turn it into Valid state, and publish the item, both the old relation and the new one proposed appear in the administration tool and in the Front end.
How to reproduce
Here's an example illustrated by screenshots to help me explain the issue.
This item has the Application Schema field, which is of type RelationReference.
Now. the Application Schema field is updated.
After clicking on "Accept clarification" a draft is created.
Now, after approving the changes instead of replacing the information with the new one, both appear.
Note: this bug has been reproduced in version v2.3.0
The text was updated successfully, but these errors were encountered:
Implemented code so the item's old relations are correctly removed. The problem was that when changing the value of the relation the new one was stored but the old one was never deleted.
This error happens when updating the information on a RelationReference type field.
If the user removes the value and selects a new one, the Registry creates a draft with the edited version. This draft has the correct information, but when approving the changes to turn it into Valid state, and publish the item, both the old relation and the new one proposed appear in the administration tool and in the Front end.
How to reproduce
Here's an example illustrated by screenshots to help me explain the issue.
![image](https://private-user-images.githubusercontent.com/64014694/271494740-e43e8504-7176-442d-804a-53a441998248.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjUwMjM2NDIsIm5iZiI6MTcyNTAyMzM0MiwicGF0aCI6Ii82NDAxNDY5NC8yNzE0OTQ3NDAtZTQzZTg1MDQtNzE3Ni00NDJkLTgwNGEtNTNhNDQxOTk4MjQ4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MzAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODMwVDEzMDkwMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTdmZDg4MTg1OGZlY2Y2ZTBjMGZlNzc4ZWNiMmI4YzdiNTU3ZTFkZTc2OTQwMWUwM2YzMTA4NTQ2Y2NhZmMxNzYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.WCBkKjhWXtdZAHutprmma6ntOQ8FmDUTLTC6e1o1jsk)
This item has the Application Schema field, which is of type RelationReference.
Now. the Application Schema field is updated.
![image](https://private-user-images.githubusercontent.com/64014694/271494810-0251862f-7c9e-43e7-bd00-1f4be163965f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjUwMjM2NDIsIm5iZiI6MTcyNTAyMzM0MiwicGF0aCI6Ii82NDAxNDY5NC8yNzE0OTQ4MTAtMDI1MTg2MmYtN2M5ZS00M2U3LWJkMDAtMWY0YmUxNjM5NjVmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MzAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODMwVDEzMDkwMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTY1ZjFlMzVkMzNiYmM3Yzg2YzEyNzgxODhiZTg3ODQxYTYxYTE5ZDZkM2I0N2FjZjRlYWMzMmY0NTQzZTdjYmQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.IQ5EqBG4XAdCBSDpn2zE-5OMcOWkpNJOZByMJypgI0w)
After clicking on "Accept clarification" a draft is created.
![image](https://private-user-images.githubusercontent.com/64014694/271494886-0adeb353-2960-4351-920e-eaf7c431d4d9.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjUwMjM2NDIsIm5iZiI6MTcyNTAyMzM0MiwicGF0aCI6Ii82NDAxNDY5NC8yNzE0OTQ4ODYtMGFkZWIzNTMtMjk2MC00MzUxLTkyMGUtZWFmN2M0MzFkNGQ5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MzAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODMwVDEzMDkwMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE0NGQ2MTllMmE2Nzg1OWU4MjM0NTU3ZmMwY2I3MjkwYWMwNGM4YWZiMGE4YzAwNjUyYzYyYTljN2VjOTQ0ZmYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.imNSRGLlDdxyyI9TYoW3IZIzx8MFupdHs41FGmgyOzM)
Now, after approving the changes instead of replacing the information with the new one, both appear.
![image](https://private-user-images.githubusercontent.com/64014694/271494958-54b1212f-3725-4870-b376-82a8892b2ca8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjUwMjM2NDIsIm5iZiI6MTcyNTAyMzM0MiwicGF0aCI6Ii82NDAxNDY5NC8yNzE0OTQ5NTgtNTRiMTIxMmYtMzcyNS00ODcwLWIzNzYtODJhODg5MmIyY2E4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MzAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODMwVDEzMDkwMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc3NDQxZjg4NWVkNTA5ZjkwMzhjMzUwZGVlMDg0YzViYWExOGEwZThjN2UxNmIxMDZjMzllODY4ODNhMzNjNzEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.TkJij9yyx8XgOGA744iy7mKkK_8_DNEBlRHEooFg590)
Note: this bug has been reproduced in version v2.3.0
The text was updated successfully, but these errors were encountered: