[UIDATIMP-456] Mapping Profiles Form existing record type recognition behavior is wrong - FOLIO Issue Tracker

XML

Word

Printable

Bug symptoms are the following:

Form loads with empty mapping details section when it loads for existing record edit mode.
When the user changes existing record type for already existing mapping profile and then returns to original existing record type, form believes nothing has changed and leaves the previous section type initial data that prevents the form from correct work behavior.

Root causes:

When the form loads with existing record in edit mode it first persists null as previous (initial) existing record type value and then loads the form data with actual value from the form state. This pushes the form logic to believe existing record type has changed and empty initial data load is needed

blocks

UIDATIMP-441 Release UIDATIMP module (1.8.1 Q1 2020 Follow-up 1)

defines

UXPROD-2075 MARC Bib Field Mapping Profiles Details for Inventory records

is defined by

UIDATIMP-15 Data Import Field Mapping Profile details: Inventory instance from MARC

UIDATIMP-290 Data Import Field Mapping Profile details: Inventory holdings from MARC Bib

UIDATIMP-292 Data Import Field Mapping Profile details: Inventory item from MARC Bib

Mapping Profiles Form existing record type recognition behavior is wrong