I think you don't need to define fme_feature_type_name or any column of your schema feature. This parameter is for your data features attributes.

Doesn't it work with fme_feature_type selected ? Can you share the full log ?

I’ve come across this before, and didn’t have the time to investigate deeper, so just added the schema to every feature. I’ll be interested to hear if this is an issue

The FeatureWriter is set up with Schema Sources as Schema From Schema Feature and Schema Definition Name as Default from Feature Class or Table name above

It returns this warning

Cannot define schema for ‘xxxxx' as the feature does not contain schema information, and schema source is set to 'Schema from Schema Feature'. Please verify writer feature type configuration
 

Followed by these errors

Esri Geodatabase Writer: Feature Type Definition xxxx' was requested, but not defined. Please visit https://www.safe.com/support
GEODATABASE_FILE writer: An error has occurred. Check the logfile above for details
 

The exact same set up using a writer works without issue.

If i switch the FeatureWriter to Esri Geodatabase (ArcSDE Geodb) that also works without issue

Hi ​@ebygomm 
I tested a simple workspace locally and it appears that the attribute “fme_feature_type_name” attribute exists. 

I am not entirely sure what is happening since ArcSDE also works as expected. 

Are you able to share your workspace (no need for data)? 
Can you try creating repeating the process in a brand new workspace? 

​@ebygomm 

Sometimes I ran into the same issue you are having. I make sure that the “Schema Feature” is at the top of the list going into the FeatureWriter. I used Sorter (fme_feature_type_name | alphabet| descending) This will make the schema be the top features before data actually written. It was able to solve the problem I having most of the time. Hopefully it will help you as well.
 

Unfortunately that was one of the first things I tried, and it makes no difference. If the schema wasn’t hitting the writer first you would expect the standard writer to fail too, but it works fine. It’s only the feature writer writing to a File Geodatabase that is the problem.

I’ve also tried using a schema scanner with the setting “Output Schema Before Data Features” set to Yes which also makes no difference.

​@rahulsharma - the workspace is literally as posted in the screenshot, a feature reader followed by a feature writer

I’m on 2024.2 and able to write the GDB dynamically.
One thing I would double check is making sure the fme_feature_type name actually matches the schema. (I know it should aways match since we not changing anything) But when I was playing with this, I have feature class name Area_Interest (ArcPro seeing as Area_Interest) but when FME reading the GDB. It recognize that feature class as Area_Inter. Like it got trim somehow, could be “reserver word” or something. After I try change Area_Interest to AOI. Now it works fine.