We are updating from 16.2.4 to 19.1.4. Seems to be working fine so far but one thing I was not able to fix.
We do not want our customers to choose if they want to have databinding or expression binding in their reports.
Expression binding seems cool and most certainly we want to use them in future formats but legacy formats should be left untouched.
I already saw the following:
Which all seem to point to some static property on the UserDesignerOptions class.
But there is no static property in 19.1.4?
A global setting would be great to prevent that dialog from showing. But since we have a custom designer dialog it's also possible to adjust that.
Please refer to the Data Binding Modes Comparison help topic for more information on how to set the default binding mode (the Set Binding Mode section) and hide the conversion dialog (the Convert Bindings to Expressions section) in the latest version of our suite. Note that our documentation provides a version selector functionality, that allows you to find information that is actual for the version that you are using.
In any case, we did not perform any changes to the code that was used to specify the static option. So, the code provided in the How to set the static DataBindingMode ticket that you found seems to have a typo. I checked the BC4186 - The default data retrieval mechanism has been changed breaking change's text and I see that the correct code is provided there. So, I corrected the code in the How to set the static DataBindingMode ticket.