Overview
You might have come across a situation where the filename changes when the file is exported outside of M-Files. The filename may have a "{2}" in it that wasn't present in M-Files. There is a good reason for this.
The "/" is a prohibited character in Windows filenames, so if a filename has that in it, the filename has to be replaced with something that works in Windows as well. The "{2}" that is used instead, tells us exactly what character was replaced, but the outcome could be "prettier". There is already an improvement suggestion available on this issue (ID #145575)
How to avoid this?
This issue in theoretically easy to resolve as you just need to make sure there are no illegal characters in your filenames in M-Files. In practice, however, there is more to this as the filename can be for example calculated from other sources. In these cases, it would be needed to check that the automatic naming convention would not use any illegal characters in it.
