Holdings are not displayed correctly in POL locations accordion after updating the ownership of one of the holdings

Description

Overview: Locations in POL “locations” accordion do not reflect the expected result. Location for pieces and instance are displayed correctly. Also if we go to POL’s edit mode, locations are displayed as expected.

Preconditions:

  • "Allow user to select locations from other affiliations for central orders" option should be checked (active) in "Settings" -> "Consortium manager" -> "Central ordering" in Central tenant

  • An order in "Open" status with one PO line has been created in Central tenant:

    • "Receiving workflow" is set as "Synchronized order and receipt quantity"

    • Quantity = 2

    • First item has holding in Member 1 tenant (e.g. "M1-Loc"), second - in Member 2 tenant (e.g. "M2-Loc1")

    • "Create inventory" is set as "Instance, Holdings, Item"

  • Authorized user with "Staff" type has affiliations in the following tenants:

    • Central

    • Member 1

    • Member 2

  • Same user has the following permissions in Central tenant:

    • Inventory: All permissions

    • Receiving: View

    • Orders: Can view Orders and Order lines

    • Settings (Consortia): Can view network ordering

  • Same user has the following permissions in Member 1 and Member 2 tenants:

    • Inventory: All permissions

    • Inventory: Update ownership

  • Same user is logged in Member 1 tenant

Steps to reproduce:

  1. Go to "Inventory" app on Instance details pane related to title selected in POL from Preconditions

  2. Click "View holding" button next to holding name (e.g. "M1-Loc")

  3. Update ownership for selected holding:

    • Click "Actions" button

    • Select "Update ownership" option

    • Select "Member 2" tenant in "Affiliation" dropdown

    • Click on any available holding (e.g. “M2-Loc2”)

    • Click "Confirm" button on appeared "Update ownership of holdings" confirmation modal

  4. Switch active affiliation:

    • Click on user profile section at the right side of top navigation bar

    • Select Central tenant in "Consortium members" dropdown

    • Click "Save & close" button

  5. Go to “Orders” app and search for the POL from preconditions

  6. Click on PO line from Preconditions

Expected result:

  • In locations accordion both records display Member 2 affiliation.

  • Holding for the first location is the one selected during ownership update on step #3 (e.g. “M2-Loc2”).

  • The second location displays the holding selected in preconditions for Member 2 tenant (e.g. "M2-Loc1").

Actual result:

  • In locations accordion both records display Member 2 affiliation.

  • First location displays the holding selected in preconditions for Member 1 tenant (e.g. "M1-Loc").

  • Second location displays “Invalid reference” as holding.

Actual result 2 (after fix):

  • In locations accordion both records display Member 2 affiliation.

  • First location displays the holding selected in preconditions for Member 1 tenant (e.g. "M1-Loc").

  • The second location displays the holding selected in preconditions for Member 2 tenant (e.g. "M2-Loc1").

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

12

Checklist

hide

Activity

Show:

Dennis Bridges December 5, 2024 at 3:47 PM

Test successful in eureka-bugfest-ramsons-consortia. The instance in the central tenant is not showing the new Holdings under the new owning tenant. However in inventory of that tenant the Holding and item appear correctly under the instance. Assuming this is a display issue that is unrelated. We discussed this issue in refinement and likely it is related to inventory display inconsistency issue.

NinaChistova December 5, 2024 at 12:27 PM

Tested on eureka-bf, works as expected (please note that linked issue in mod-search is still active, and “Invalid reference” is displayed, but POL holdings contain correct IDs)

 

could you please review? Thank you!

Oleksii Petrenko December 5, 2024 at 11:57 AM
Edited

Please retest was closed

NinaChistova December 5, 2024 at 9:13 AM

Instance could not be found, verification is blocked by

JenkinsNotifications December 5, 2024 at 5:50 AM

Deployed to the Ramsons bf env. Moved status to In bugfix review from status Awaiting deployment. Please proceed with the verification.

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Thunderjet

Fix versions

Release

Ramsons (R2 2024) Bug Fix

RCA Group

TBD

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created October 24, 2024 at 10:08 AM
Updated December 5, 2024 at 3:47 PM
Resolved December 4, 2024 at 2:44 PM
TestRail: Cases
TestRail: Runs