As someone who is in the App Editor 24/7, I frequently catch myself trying to remember the syntax for a particular expression, re-reading a formula several times to figure out where my missing parentheses are, or searching my mind for some fancy formula I put together ages ago.
I know many of you have experienced the same.
To make life a little easier on our favorite app making platform, the QREW Technologies team has released the first version of a Chrome Extension, QREW TOOLS, that adds some cool features to help address those pain points:
LIVE EXPRESSION FORMATTING
IN-EDITOR DOCUMENTATION SEARCHING
SAVE AND INSERT CUSTOM FORMULA SNIPPETS
I hope you guys enjoy this and that it helps you get more enjoyment and productivity out of the AppSheet Platform.
Please give me a shout if you have any feature suggestions or find any bugs
Just awesome @Stefan_Quartemont! I will definitely need to try this out! Really something that should be in then native editor. Maybe the Appsheet team can use this as an example to drive future editor enhancements. Thanks for the effort and for sharing!
Now just add a library of @Steve ‘s best collection of formula examples and this could be huge
On the right track (or one of 'em, at least): HOUR() requires a Duration as input rather than a DateTime, so you need to convert [Barrel Drop Off Date/Time] by subtracting a zero time from it: HOUR([Barrel Drop Off Date/Time] - “00:00:00”). HOUR() returns a Number rather than a Time, so you’ll be working with 9, 10, 11, 12, 13, 14, 15, etc. IN() expects a list as the second argument, not a range, so the off-hours need to be expressed in a list: IN(…, LIST(15, 16, 17, 18, 19, 20, 21, 2…
Here I read: These snippets are stored in local browser memory, so clearing your browser memory WILL DELETE any saved snippets. We do not receive this data.
Can we sync the Snippets over different Chrome Profiles?
Could we do a Google Drive sync with the Snippets?
Great questions. The ideal scenario is that we’d store these snippets in the cloud for you, so you could have access beyond the life of the browser memory. It takes more development and has an added cost to it, so we wanted a lighter approach to start with.
Storing it in such a way that it syncs with that same chrome profile across devices is not to difficult, though. I’d have to test if it gets deleted as the browser data gets cleared.
I’ve also considered an option to mass download/upload, but that seems more like an inconvenient work around rather than a fix
On the right track (or one of 'em, at least):> > - HOUR() requires a Duration as input rather than a DateTime , so you need to convert [Barrel Drop Off Date/Time] by subtracting a zero time from it: HOUR([Barrel Drop Off Date/Time] - "00:00:00") .> - HOUR() returns a Number rather than a Time , so you’ll be working with 9, 10, 11, 12, 13, 14, 15, etc.> - IN() expects a list as the second argument, not a range, so the off-hours need to be expressed in a list: IN(..., LIST(15, 16, 17, 18, 19, 20, 21, 22, 23, 0, 1, 2, 3, 4, 5, 6, 7, 8)) .> > Which gives you:> > auto> NOT(> IN(> HOUR(> [Barrel Drop Off Date/Time]> - "00:00:00"> ),> LIST(> 15, 16, 17, 18, 19, 20, 21, 22, 23,> 0, 1, 2, 3, 4, 5, 6, 7, 8> )> )> )> > > > That tests for times outside allowed hours. You could instead test for times within allowed hours:> > auto> IN(> HOUR(> [Barrel Drop Off Date/Time]> - "00:00:00"> ),> LIST(9, 10, 11, 12, 13, 14)> )> > > > Or, if you want to allow for time constraints that fall off the top of the hour, you can use full times:> > auto> AND(> (TIME([Barrel Drop Off Date/Time]) >= "09:00:00"),> (TIME([Barrel Drop Off Date/Time]) < "15:00:00")> )> >
@mike, you could certainly save that whole things as a snippet, but it would be cool to have a place in the Documentation site for user generated expressions/implementations that is easily searchable
@Stefan_Quartemont I tried this out but found that the SNIP button overlays or replaces the expand the expression window button in the bottom right-hand corner of the expression editor window as shown below. This means for longer expressions one has to now manually scroll. Can this be resolved ?
