ID 599371 - Parameter Tab UI is incorrectly generated when loading a scene with an isolate node containing an expression

Follow

Problem summary
Parameter Tab UI is incorrectly generated when loading a scene with an isolate node containing an expression
 
Customer reported version
Katana 7.5v3
 
Customer reported platform
Rocky 9 
 
Steps to reproduce
 
1) In Katana, load the attached example scene: IsolateNodeExpression.katana

2) Set the edit flag (e) on the Isolate node and observe the isolateLocations parameter.
 
Without an example scene
 
1) In Katana, create an Isolate node and set the edit flag (e) on the node.
 
2) In the Parameters tab, select 'Add Locations' under the isolateLocations parameter and select Expression. Observe the same error generated below.
 
Expected behaviour
The isolateLocations parameter loads the saved expression without error.
 
Actual behaviour
After loading the scene (or attempting to create an expression under the parameter), the UI of the Parameter tab is generated incorrectly, can't be regenerated and produces the following error:
[ERROR python.root]: A TypeError occurred in "KatanaFactory.py": unhashable type: 'dict'Traceback (most recent call last):File "ValuePolicy.py", line 407, in _HandleQueuedChangesFile "WeakMethod.py", line 40, in callFile "Widgets/SortablePanel.py", line 215, in valueChangedEventFile "FormMaster/Editors/LocationEditor.py", line 239, in updatePanelsFile "FormMaster/Editors/LocationEditor.py", line 451, in createExpressionPanel File "FormMaster/Editors/ScenegraphLocationArray.py", line 395, in __initFile "FormMaster/KatanaFactory.py", line 229, in LookupWidgetTypeTypeError: unhashable type: 'dict'
Workaround
Unknown.
 
Reproduced by support
This bug has been reproduced in:
Katana 8.0v3 - Windows 11 / Rocky 9
Katana 7.5v3 - Windows 11 / Rocky 9
Katana 7.0v6 - Windows 11 / Rocky 9
 
Unable to reproduce bug in:
Katana 6.5v5 - Windows 11 / Rocky 9
 
Earliest version tested
Katana 6.5v5 - This issue doesn't appear in this version and has regressed
 

    We're sorry to hear that

    Please tell us why