Search Issue Tracker
Fixed
Fixed in 2023.2.15f1, 6000.0.0b12
Votes
0
Found in
2023.2.4f1
2023.3.0b1
6000.0.0b11
Issue ID
UUM-59593
Regression
No
UI Builder data binding window shows incorrect data source paths when type is selected and there is an inherited data source
How to reproduce:
1. Open the attached “uibuilder_databinding_issue” project
2. Open the UI Builder window (Window > UI Toolkit > UI Builder)
3. In the UI Builder, open “MyDocument” (Click the project button and navigate to “Assets/Mydocument.uxml”, right-click > open in UI builder)
4. Select the Label in the UI Builder hierarchy
5. In the UI Builder Inspector, right-click the “Text” field and select “Add binding”
6. Select “Type” in the newly opened window and type “AnotherDataSource” in the field just below the button
7. Select the “Data Source Path” field and observe the results
Expected result: Data Source Path suggests fields belonging to “AnotherDataSource”
Actual result: Data Source Path suggests fields belonging to “MyDataSource”
Reproducible in: 2023.2.4f1, 2023.3.0b1
Could not test with: 2021.3.34f1, 2022.3.17f1 (feature does not exist)
Reproducible on: macOS 14.0, Windows 11
Not reproducible on: No other environments tested
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note (fix version 6000.0.0b12):
Fixed code path to retrieve the correct data source path.
Resolution Note (fix version 2023.2.15f1):
Fixed code path to retrieve the correct data source path.