When sending an SMS message from an automation, the AppSheet_Default_SMS setting in the Via channel property is no longer supported for new tasks. Moving forward, use a personal Twilio account to send SMS messages through automation.
Enhancement
[_THISROW_BEFORE] and [_THISROW_AFTER] are now supported inside a set column action in an automation. This update will be rolled out gradually. It is currently deployed to 50% of free users.
Bug fixes
None
Rollout changes
None
Preview announcements
Preview feature releases enable you to try out new app features that are not yet fully supported. See Product launch stages.
No new preview features were released today.
In addition, the AppSheet preview program lets app creators try out new app features that are not yet fully supported. For more details and to opt-in, see AppSheet preview program.
I don’t immediately see a lot of benefit in providing the autocompletion when there is only a single table in context. But if you do see benefits, please let me know why this is useful to you and I will happily consider adding support. Thanks!
I occasionally use [_THISROW] instead of an explicit reference to the key column, in the vein of using [_THIS] rather than referencing the current column explicitly. It makes reusing the expression segment easier. Because this is valid, I feel autocomplete should support it.
Autocompletions are at an awkward intersection of wanting to support everything that is valid within AppSheet (I.e. help power users like yourselves) and wanting to make it easy for new users to learn the expression language.
For power users, I 100% agree that both of those would be somewhat useful.
For new users:
I want them to use USERSETTINGS instead of _THISUSER, as this is consistent with what it is called in the app, and less complicated than a dereference.
I don’t want them wondering what _THISROW is when there is a single scope, because _THISROW is complicated. It is necessary in a multi-scope situation, but not necessary in single scope.
Accordingly, I don’t anticipate adding support for those at this time.
(Though I want to emphasize that I do appreciate you sharing your voices – community opinions like yours have helped me develop a better understanding of the expression power user experience and definitely does influence and enhance expression related development)
@wabrian , thanks for the response. I completely understand your perspective here. Perhaps in the future, there might be an “I am a power user” option in the editor settings.
