In qgis 3.28.4 when I export a gpkg as a .gdb I can see the separate fields of the layer in the Browser panel.
As soon as I add a Field Domain to the gdb, the Browser panel no longer shows the separate fields. Therefore, I cannot append the created field domain to a specific field.
However, opening a new instance of QGIS, or closing and opening QGIS the Browser panel does correctly show the layer fields and the Field Domians.
Steps to reproduce the issue
using qgis 3.28.4 on Windows 10 pro
take any gpkg with existing fields
export as file geodatabase .gdb
check in browser panel that you can see the layer fields (picture 1)
add a New Field Domain > New coded values domain to the .gdb
As soon as it is added, the Browser panel no longer shows the layer fields (picture 2)
Now, if you close and open qgis, or open a second instance of qgis the Browser panel does correctly show the layer fields and the Field Domains (picture 3)
Versions
QGIS version | 3.28.4-Firenze | QGIS code revision | fd0fb72ab3
-- | -- | -- | --
Qt version | 5.15.3
Python version | 3.9.5
GDAL/OGR version | 3.6.2
PROJ version | 9.1.1
EPSG Registry database version | v10.076 (2022-08-31)
GEOS version | 3.11.1-CAPI-1.17.1
SQLite version | 3.39.4
PDAL version | 2.4.3
PostgreSQL client version | unknown
SpatiaLite version | 5.0.1
QWT version | 6.1.6
QScintilla2 version | 2.13.1
OS version | Windows 10 Version 2009
| | |
Active Python plugins
batchvectorlayersaver | 0.9
BGTImport | 3.16
GroupStats | 2.2.6
inspireatomclient | 0.8.1
maplibrary | 1.2
pdokbaggeocoder | 0.6.6
pdokservicesplugin | 4.1.2
pdok_locatieserver_locator_filter | 0.2.1
plugin_reloader | 0.9.3
qgis2web | 3.16.0
QNEAT3 | 1.0.4
QuickWKT | 3.1
quick_map_services | 0.19.33
refFunctions | 1.6
RuimtelijkePlannen | 3.5.2
SpreadsheetLayers | 2.1.0-alpha1
wfsclient | 0.9.11
db_manager | 0.1.20
grassprovider | 2.12.99
processing | 2.12.99
sagaprovider | 2.12.99
QGIS version
3.28.4-Firenze
QGIS code revision
[fd0fb72ab3](https://github.com/qgis/QGIS/commit/fd0fb72ab3)
Qt version
5.15.3
Python version
3.9.5
GDAL/OGR version
3.6.2
PROJ version
9.1.1
EPSG Registry database version
v10.076 (2022-08-31)
GEOS version
3.11.1-CAPI-1.17.1
SQLite version
3.39.4
PDAL version
2.4.3
PostgreSQL client version
unknown
SpatiaLite version
5.0.1
QWT version
6.1.6
QScintilla2 version
2.13.1
OS version
Windows 10 Version 2009
Active Python plugins
batchvectorlayersaver
0.9
BGTImport
3.16
GroupStats
2.2.6
inspireatomclient
0.8.1
maplibrary
1.2
pdokbaggeocoder
0.6.6
pdokservicesplugin
4.1.2
pdok_locatieserver_locator_filter
0.2.1
plugin_reloader
0.9.3
qgis2web
3.16.0
QNEAT3
1.0.4
QuickWKT
3.1
quick_map_services
0.19.33
refFunctions
1.6
RuimtelijkePlannen
3.5.2
SpreadsheetLayers
2.1.0-alpha1
wfsclient
0.9.11
db_manager
0.1.20
grassprovider
2.12.99
processing
2.12.99
sagaprovider
2.12.99
### Supported QGIS version
- [X] I'm running a supported QGIS version according to the roadmap.
### New profile
- [X] I tried with a new QGIS profile
### Additional context
_No response_
Just tested this in 3.34.7 and 3.36.3 and it is still here.
This bug does not happen when creating field domains on a GeoPackage, only on a FGDB created in QGIS
What is the bug or the crash?
In qgis 3.28.4 when I export a gpkg as a .gdb I can see the separate fields of the layer in the Browser panel. As soon as I add a Field Domain to the gdb, the Browser panel no longer shows the separate fields. Therefore, I cannot append the created field domain to a specific field.
However, opening a new instance of QGIS, or closing and opening QGIS the Browser panel does correctly show the layer fields and the Field Domians.
Steps to reproduce the issue
using qgis 3.28.4 on Windows 10 pro
take any gpkg with existing fields
export as file geodatabase .gdb
check in browser panel that you can see the layer fields (picture 1)
add a New Field Domain > New coded values domain to the .gdb
As soon as it is added, the Browser panel no longer shows the layer fields (picture 2)
Now, if you close and open qgis, or open a second instance of qgis the Browser panel does correctly show the layer fields and the Field Domains (picture 3)
Versions
QGIS version | 3.28.4-Firenze | QGIS code revision | fd0fb72ab3 -- | -- | -- | -- Qt version | 5.15.3 Python version | 3.9.5 GDAL/OGR version | 3.6.2 PROJ version | 9.1.1 EPSG Registry database version | v10.076 (2022-08-31) GEOS version | 3.11.1-CAPI-1.17.1 SQLite version | 3.39.4 PDAL version | 2.4.3 PostgreSQL client version | unknown SpatiaLite version | 5.0.1 QWT version | 6.1.6 QScintilla2 version | 2.13.1 OS version | Windows 10 Version 2009 | | | Active Python plugins batchvectorlayersaver | 0.9 BGTImport | 3.16 GroupStats | 2.2.6 inspireatomclient | 0.8.1 maplibrary | 1.2 pdokbaggeocoder | 0.6.6 pdokservicesplugin | 4.1.2 pdok_locatieserver_locator_filter | 0.2.1 plugin_reloader | 0.9.3 qgis2web | 3.16.0 QNEAT3 | 1.0.4 QuickWKT | 3.1 quick_map_services | 0.19.33 refFunctions | 1.6 RuimtelijkePlannen | 3.5.2 SpreadsheetLayers | 2.1.0-alpha1 wfsclient | 0.9.11 db_manager | 0.1.20 grassprovider | 2.12.99 processing | 2.12.99 sagaprovider | 2.12.99 QGIS version 3.28.4-Firenze QGIS code revision [fd0fb72ab3](https://github.com/qgis/QGIS/commit/fd0fb72ab3) Qt version 5.15.3 Python version 3.9.5 GDAL/OGR version 3.6.2 PROJ version 9.1.1 EPSG Registry database version v10.076 (2022-08-31) GEOS version 3.11.1-CAPI-1.17.1 SQLite version 3.39.4 PDAL version 2.4.3 PostgreSQL client version unknown SpatiaLite version 5.0.1 QWT version 6.1.6 QScintilla2 version 2.13.1 OS version Windows 10 Version 2009 Active Python plugins batchvectorlayersaver 0.9 BGTImport 3.16 GroupStats 2.2.6 inspireatomclient 0.8.1 maplibrary 1.2 pdokbaggeocoder 0.6.6 pdokservicesplugin 4.1.2 pdok_locatieserver_locator_filter 0.2.1 plugin_reloader 0.9.3 qgis2web 3.16.0 QNEAT3 1.0.4 QuickWKT 3.1 quick_map_services 0.19.33 refFunctions 1.6 RuimtelijkePlannen 3.5.2 SpreadsheetLayers 2.1.0-alpha1 wfsclient 0.9.11 db_manager 0.1.20 grassprovider 2.12.99 processing 2.12.99 sagaprovider 2.12.99 ### Supported QGIS version - [X] I'm running a supported QGIS version according to the roadmap. ### New profile - [X] I tried with a new QGIS profile ### Additional context _No response_