Issues with Dynamic Form Rules after Sunday's Rich Text Update
I am posting this in a new post as the current one addressing this is hard to find. In the latest release this Sunday, 12/17/2017, QB support confirmed to me that they automatically updated various text fields whereby the "Allow HTML" checkbox was checked to Rich Text fields. This affected most Text fields and Formula Text fields.
Among other possible effects which are not known, one effect of this change that I can confirm in my apps is that it has broken the functionality of some Dynamic Form Rules. Specifically confirmed is when you have a Form Rule that is supposed to update a Field (now Rich Text) with values. For instance, I have a what was once a Text Field with the "Allow HTML" checkbox checked that is now a Rich Text field through QB's wisdom. My former Text (Multi-Line) field on the form page no longer updates when someone checks a box that is supposed to populate it with certain text data, as per my Form Rule.
My resolution was to go into the field properties and change it back to Text (Multi-Line). If I change it back to Rich Text again, it still does not work. In my case, this field doesn't need to allow HTML, but for some people this is broken and I am not sure of the resolution if you need html in the field to be read as html.
Please feel free to provide any additional information you may know in this thread.
Among other possible effects which are not known, one effect of this change that I can confirm in my apps is that it has broken the functionality of some Dynamic Form Rules. Specifically confirmed is when you have a Form Rule that is supposed to update a Field (now Rich Text) with values. For instance, I have a what was once a Text Field with the "Allow HTML" checkbox checked that is now a Rich Text field through QB's wisdom. My former Text (Multi-Line) field on the form page no longer updates when someone checks a box that is supposed to populate it with certain text data, as per my Form Rule.
My resolution was to go into the field properties and change it back to Text (Multi-Line). If I change it back to Rich Text again, it still does not work. In my case, this field doesn't need to allow HTML, but for some people this is broken and I am not sure of the resolution if you need html in the field to be read as html.
Please feel free to provide any additional information you may know in this thread.
