Hi, the community is there to help. Can you please provide some additional information - which transformers, which file gdb writer - and/or some sample data and workspace to reproduce the issue? Doesn't sound too complicated what you are doing, creating points from lat/long coordinates, but apparently something goes wrong somewhere...

Hello, egge.

You're right, it's a pretty simple process. There's an excel reader, feeding into an AttributeManager (that renames some of the columns), then a file geodatabase writer - the type is ";GEODATABASE_FILE]" or "Esri Geodatabase (File Geodb)" depending on where you look. That's all there is. I have had the same results even if I don't use the AttributeManager and just rename the columns in the writer instead.

I also tried using a vertexCreator, in case the problem was with the writer, but the results were the same.

I will have to see about the possibility of sharing sample data. My workplace has strict rules about data sharing and I expect would require me to get an NDA signed beforehand.

It turns out that I was using a word as a column name that is reserved by something. I had a column named 'Group' and that was evidently offending Arc Pro somehow. Someone suggested I change that name and then the problem went away.

Good to hear the issue has been solved. So, it was an Arc Pro and not an FME problem after all 🙂

Now, to finish everything off you may wish to close the call by marking your last answer as the right one. (No, this will not earn you any points, but at least it will be clear to the community that your question has been answered.)

The solution and the problem turned out to be very trivial, but it was interesting.

Here is the ESRI documentation I was directed to that lists reserved words for file geodatabases:

FAQ: What Are the Reserved Words for Esri's File Geodatabase?