I encountered an error when writing data to a geodatabase because the file path contains a dot (period), even though this naming convention is completely valid. Everything worked fine in previous versions, but it fails in FME 2026.1. For example, I want to write to a Geodatabase named 'Geo.A1.2552.gdb'.
Is this a known bug?
Solved
Can not write geodatabase if the path contains special characters?
+8- Supporter
Best answer by j.botterill
Could be a regression, but no doubt the parsing logic for Esri gdb readers and writers has become stricter. For example, updated GDAL/Esri API bindings
A . in a folder name can be misinterpreted as a file extension boundary or can interfere with underlying Esri API calls (should you use Portal enterprise/AGOL).
My simple ESRI rule of thumb for files, attribute naming etc:
- no whitespace in paths
- underscores only
- characters only
So, I recommend the most consistent permanent fix would be naming your output Geo_A1_2552.gdb
+60- Influencer
- Best Answer
Could be a regression, but no doubt the parsing logic for Esri gdb readers and writers has become stricter. For example, updated GDAL/Esri API bindings
A . in a folder name can be misinterpreted as a file extension boundary or can interfere with underlying Esri API calls (should you use Portal enterprise/AGOL).
My simple ESRI rule of thumb for files, attribute naming etc:
- no whitespace in paths
- underscores only
- characters only
So, I recommend the most consistent permanent fix would be naming your output Geo_A1_2552.gdb
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.