For all components please allow an option to have the component appear even if there is no data in the field. The UI changes depending on what data has or has not been entered, which makes it harder to make consistent screens. And also, when viewing, the user may not know which fields are missing da…

An alternative would be to remove headings from all of your components, but instead use text or rich text components as your headings.

Another alternative would be to initiate you data points. Let’s take “phone number” as an example. It could be anything else you expect your users to submit. You can create 3 columns: Phone_No_Initiate (or Phone_No_Default): a template column or a single value column, whose value will be non-emp…

[image] nathanaelb: Phone_No_Initiate (or Phone_No_Default): a template column or a single value column, whose value will be non-empty for each new row. For example – or - . This column is actually redundant. You could just use a single if-then-else column, ie: If Phone Number is empty, the…

Totally agree, three columns could be reduced to two, but I prefer not to. I use this method quite often, mainly for user-submitted data that’s not required, including images. For images, I’ll use the “Generate Image” column (only if the list is short, because the experience may become sluggish if t…

[image] nathanaelb: I like seeing my data in tables. That way I might remember it’s there. I would feel uncomfortable if default data were “hidden” in a field of a ITE column. But maybe that’s just me This is a good point. And it’s similar to the mantra of avoiding Magic Numbers in programmin…

Hm…good insight on magic numbers. Apparently I use magic numbers all the time…might need to rethink my methods.

hehe yeah, I’ve picked up on that in some of your videos but didn’t say anything :slight_smile: I think with Glide, it’s probably a matter of striking a balance between avoiding it and winding up with an excessive amount of columns. But when it comes to coding, I try to be a bit disciplined about …

I like that concept a lot! I’m no programmer I had never heard of magic numbers before, but we do see them quite a bit. Do you consider the +15 or +15+30 from the first day of the month to be a magic number? The first time I saw Jeff’s method, I found the approach both really smart and uncomfortabl…

Hehe. It’s like the “answer to everything”…I should have went with 42 instead. :wink: The reason I went with 15, is that it puts you approximately in the middle of the month, so when you add months or years based on the average number of days in a month, it would keep you somewhere in the middle …

I find the formula and thinking behind it incredibly smart, don’t get me wrong. I was just wondering if we could put that +15 in the magic number category : )

Show Component Always

Feature Requests

Jeff_Hager June 5, 2022, 12:54pm 16

I think this is the latest iteration of the formula to add months to a date, which handles leap year or end of month situations.

Topic		Replies	Views
All New Data Editor & Computed Columns General	94	3002	November 19, 2021
Fun with Dates Project Showcase	156	6939	April 19, 2022
New computed column: Math General	96	6351	November 12, 2021
New item/row with defaults set from most recent Ask for Help	24	951	October 4, 2022
Pages Missing Components Feature Requests	97	3129	August 20, 2023

Show Component Always

Related topics