Write to a zipped file geodatabse

Hi ​@fme_hans thanks for your question. I just tested this and seems to work for me, so I’m wondering how you have your writer set up and what version of FME you are using. I tested with 2024.2.1 and this is what my workspace looks like:
 

Let me know! Any additional details you could provide would be helpful.

Hi, my setup is different. I have 4 different featurewriter transformers that each fill 1 feature class in the zipped file geodatabase. The first featureclass get filled, the others not.

​@fme_hans ah, you have FeatureWriters instead. You should also make sure that you are writing to a .zip by making sure that it is included at the end of your file name in your FeatureWriter. When a .zip is specified it should also have the icon on the far left of the path indicating that it will be zipped. I’ve highlighted both in my screenshot:

Also, if you are writing to the same GDB you should probably only use one FeatureWriter as you can connect multiple Feature Types within like I have. In my screenshot you can see that both ‘Parks’ and ‘Living_Areas’ are included in the one FeatureWriter. 

Now I haven’t seen all of your parameters for each of your feature types, but I suspect that they do not have the same writer and therefore are either different files or overwriting the same file each time so you only end up having one Feature Type in the GDB. For my overwriting assumption, you should make sure that ‘Overwrite Existing Geodatabase’ in the writer parameters is not checked. Since FeatureWriters can be placed anywhere in your workflow and do not need to execute at the end of the workspace, this could actually happen depending on how complex the workspace is.