Word Document Template Error! Unknown document property name After 22.3 Update

We paused the automatic updates almost right after this issue was found, and as of tomorrow April 1st, the new version of M-Files should be available through the Automatic updates service and through our website on April 1st. And no.. unfortunately this is not an Aprils fools thing :D No Easter eggs hidden.. 

As of writing this, the website is not yet updated. The new version label will be 22.3.11237.6.

Apologies of the inconvenience. 

Hi,

Installed 22.8.11717.3 but still "Error! Unknown document property name". Is there something to do ?

Thanks

The issue I think is on client level, not server level. So he would need to download only clients installations.

You're right. Downgrading to version 22.6.11534.4 did the trick for now. Waiting for a definitive fix now.

Automatic updates are now disabled...

Thanks

Is 22.6 available on the website?

You can find it here : cdn3.m-files.com/.../M-Files_Online_x64_eng_22_6_11534_4_EV.msi

Can you also fix this in one go?

https://community.m-files.com/forums-1552881334/f/m-files-clients/6208/office-add-in-get-properties-from-related-document

Inserting properties from Related Document is not working..

Hello.  Installed 22.8.11717.3 and we have the same problem. We have 256 templates with the error and Electronic Sign Advanced, this is critical for us. There is a ticket ID 164624

Hello, 

September release should have this fixed now. (version 22.9).

Regards,

Radu

Is it also fixed that you cannot get Properties of a related Document?

I don't think so. Did that ever worked?

Maybe it is no Bug, but I think this still could be fixed (or changed)..

Better let the customer decide on this and not restrict things like this.. I would even go further and unify functionality of standard and document object type.. Why class groups only for documents? Senseless restriction in my opinion..

Maybe it is no Bug, but I think this still could be fixed (or changed)..

Better let the customer decide on this and not restrict things like this.. I would even go further and unify functionality of standard and document object type.. Why class groups only for documents? Senseless restriction in my opinion..