Creating a new column : A/Content3 should be placed right after A/Content2 iso B/Content2.
A/content A/content2 B/Content B/Content2
Hope youāve got what I mean
Creating a new column : A/Content3 should be placed right after A/Content2 iso B/Content2.
A/content A/content2 B/Content B/Content2
Hope youāve got what I mean
Turn on the discount/coupon field in the Stripe checkout screen
@Mark Is this possible?
One thing I noticed from the last session ---- I think @Jason increased the time delay for notifications and adjusted their width for longer messages. This is great, but I think the notification box should disappear if someone interacts with another part of the app while the message is displayed. Iām finding that the message is sticking around while Iām able to navigate elsewhere in the app.
Nice! Been saving this list since the last session:
@Mark @Jason @Tristan
Very simple feature to have a condition to change user profile photo
You mean to have a condition to allow/disallow changing it?
@Mark Yup, because sometimes we create dual apps and we importrange the user table in Gsheet and sometimes the users upload and they simple miss the importrange formula
We managed to have a workaround to catch their details and zapier it to the source sheet
Clear whole column values
Yes please!!!
+1
So much needed
@mark one thing I would really love is the ability to sort a joined list (Iām pretty sure Iāve asked for this before).
Use case: I build a lot of CSS/HTML tables using relations and joined lists. The results are great, but the one annoyance is that there is no way to sort the rows, and so I wind up with apparently randomly ordered tables. Here is an example:
In the above example, the table rows are formed by a joined list of template columns. What Iād love to be able to do is specify an āOrder Byā column when configuring the joined list column.
I hope this makes sense.
PS. Iām pretty sure @Jeff_Hager would also like to see this one
Itās so simple in Yes-Code, but thatās another story
Just coming back to add one more (not sure someone has/had asked for it in past).
-Shiv
An easy oneā¦a counter column !!
Allow us to configure āon submitā for the ābackā button of a ādetailsā screen. First use that comes to mind is āif order is empty, delete rowā⦠Iām sure there could be just as many uses as the current āon submitā confit.
Yes! Just likeā¦ahemā¦conditional relations⦠sometimes I need to perform some logic within the data before it even makes it to the appās front end, which is currently the only place where we can filter and sort data. In situations that Iāve ran into, sorting and filtering on the front end is too late. It needs to happen in the data because it affects the results of other computed columns. In my case, I have to use either additional google sheet tabs with queried data, or in one case, an entirely separate Google spreadsheet with import range formulas to move data back and forth between spreadsheets to offload calculations and return results that I couldnāt handle efficienctly in the appās spreadsheetā¦and this actually speeds up my appā¦
Iām so used to working with SQL directly against a DB, or Linq style queries against data tables. Shoot, even old school key lists against physical and logical files on ibm mainframes allow for rudimentary sorting and filtering of data before working with it.
Iāve just been waiting patiently and checking staging periodically in the hopes that a feature like this comes along, but I imagine itās maybe a little more than a quick change.
Until you need to create a relation where the source row has a date, and you want to find related rows based on a key, and that also have a date prior to that source date. Then rollup a sum from that relation. Currently impossible within glide, unless you want to create the most horrendous array that includes your main key values and a date as an array for every possible date you hope to relate to (imagine an array of 180 or 365 items, just to check for every possible match within 6 to 12 monthsā¦and then dynamically build that for each relation source row based on itās own date). Glide relations canāt handle data where you need to search by a range. In SQL this would be simple with a JOIN and a āWHERE rel_date<src_dateā.
Yes! Actions for:
Would be the dream⦠but not sure that itās an easy piece of work for a ālive sessionā.