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.
- 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