Share
Report
635Please be so kind as to read my full post before responding.
Thank you for your consideration.
I recently noticed that, using the feature "Relational data, options sets, and other new features for CDS", my two-value/boolean fields from Dynamics don't seem to be directly compatible with booleans in PowerApps anymore.
Thus, the use of Conditional statements or CheckBoxes or such has also been turned extremely irritating.
The following screenshots shows a record userConfig from a Dynamics entity with a two-value/boolean field kk_auto_ocr, which, using the new CDS OptionSet feature, is now a OptionSetValue type in PowerApps.
As far as I recall, two-value/boolean fields in Dynamics were given as underlying numerical value in PowerApps, which were directly compatible with PowerApps booleans.
Now, I have to use this tiresome, ugly workaround
record.booleanFieldName='booleanFieldDisplayName'.trueValue
In particular, when using several two-value/boolean fields, this gets extremely irritating.
When using 'Column display names' (default with new PowerApps since a few versions), this becomes
which is slightly less confusing, but still very irritating and tedious, in particular if I have to repeat this several times for different fields.
Also, it appears that this statement seems to not work offline since the "ColumnName.TrueValue" statement seems to require an online server call/response to retrieve the corresponding OptionSetValue, i.e. Connection.Connected mandatory.
My questions:
- Is there any chance, the old direct compatibility between Dynamics booleans and PowerApps booleans can be retained even when using "Relational data, options sets, and other new features for CDS"?
For my own development, I do appreciate these new features for LookUp fields and MultiSelect OptionSet fields.
But, I don't see any usefulness in the current state of handling booleans. - Is there a more direct, less tedious way to convert the OptionSetValue to a boolean (or numerical value)?
I don't consider saving the True/False OptionSetValues as variables less tedious.
All responses (
Answers (
