Word shows error when editing M-Files template

When you say they leave the property empty, does that mean that the property is still on the document but just with no value, or is the property not present at all?

The latter is not likely to work. The former can probably be fixed by editing/refreshing the template to make sure the inserted code in Word is formatted correctly.

Upon further investigation, it seems this error is only shown, when properties are referrenced which are not directly on the document.

In my case, I use a placeholder for "Signature" on the template, in which M-Files Users (which is an object type on his own) can be selected. Furthermore I use "E-Mail", which is a property on the before mentioned M-Files User, so referrenced via the "Signature" object type. Only for this "E-Mail" placeholder, the error is shown, but not for the "Signature" element if left empty.

Hopefully my german screenshot will help clarifying the situation

which results to the error message (there are brackets around the E-Mail placeholder, so the error refers 100% to the e-mail element):

It seems like I have to resolve this issue somehow within word, like not show placeholder when empty or something.

As long as the "Unterschrieben von" property is present on the document you should be able to use indirect reference as Unterschrieben von.E-Mail.

I would be surprised if that does not work. It may show an error in the template because you probably don't have any values in "Unterschrieben von" on the template, but it should work just fine on new documents provided those documents have a value in that property.

You could temporarily add something in "Unterschrieben von" when editing the template and then remove this again after having saved the template but before you check it in.

You could consider editing the code in Word to show nothing if the formula results in a error. There are a few posts on that subject, I believe.

Hi Thomas, We have been seeing this behaviour since august 2022 at some customers but still not a definitive fix for this issue.  Some attempts have been done during the past months but it now seems like there is a 'partial' fix but it has not maintained in the februar release.  It might make it into the march release but not sure....  Surprised that there are not more mentions of this and that it takes nearly half a year to solve this...