Hi @mazi​ Yes, the option has been removed intentionally. Why do you want to save a workspace to a mapping file?

Thank you for the very quick answer ! The mapping file will be in use by other members of my department. We have used mapping files for this purpose since years. The users can easily access the routine and the quick translator by doubleclick and additionally I can prevent the users from editing, viewing and (accidentally) changing the workspace. I have already found the workaround by using a password for the workspace in the forum. Since we never encountered any problems with the mapping files, I thought it unlikely, that the option was removed.

I agree with @mazi​ , mapping file is useful in some cases.

You can still save a workspace as a mapping file in the current version of FME Workbench.

Try changing the file extension from fmw to fme manually in the Save As dialog when you save the workspace.

Hi takashi, actually this was my first trial thinking, that the missing option is a bug, and hoping, that by choosing the .fme file extension I can trigger the creation of the mapping file. But doubleclicking the so created file resulted in opening the quick translator which instantly ran in an error because of the missing input file. (unfortunately the dialog where the user could provide the input file didn’t open). Probably I have to check the settings of the user parameter for the input file again. Do you know, when and why the option Save As .fme was removed from the dropdown menu? In the Safe Software’s documentation this option can still be found.