Hi! Is there a way to limit the number of images a user uploads using the Image Picker component?
Thanks
The only way I can think of to do this would be to use a Custom Form. The images would then be loaded into a User Specific Multiple Images column, you could do a rollup on that to get a count, and then show a message to the user and prevent them from submitting the form if the count exceeds whatever threshold you set.
2 Likes
You can create a rollup column and display it through a message with the hint component.
And prevent submission through the method in the following link:
2 Likes
Thanks but this is just a warning message right?
For prevent submission follow the link above.
1 Like
@Himaladin I admittedly haven’t tried your method yet. I think Robert’s video demonstrating your method only relied on basic columns instead of computed columns. It’s always been my understanding that computed columns were inaccessible or not computed from within a native form.
Based on what you are saying here, and what you had shown back in January, would it be correct that computed columns do actually compute within a native form, but are only accessible for visibility conditions? I have a different use case where I need to submit computed columns with my form, but I’ve never been able to access them in a native form, so I’ve had to use a custom form instead. Just curious if I’m missing something that I didn’t know was possible.
Yes… I don’t know how deep/complex it is… but almost all the computed columns I use work well, as long as you return them as true-false or empty-not empty, except for displaying their values. I mentioned at the end of my thread, even dates and times can be used. I have nested validations (many columns) as long as they ultimately result in true-false, they also work well to display the hint component.
Although there are many limitations imposed by Glide, I feel there is a spirit wandering around in the application. The Hint component is just one of its manifestations. You can also use other components and if assisted by CSS, making this new application is quite enjoyable.
1 Like
That’s good to know. Too bad they don’t make some of that stuff more accessible since they are doing the computations. Could eliminate almost any need for custom forms.
1 Like
Yes… I remember my professor’s words: “what ought to be” and “Deontic.”
Do you remember the pseudo :has I used, and its usage always being rejected by GPT? Sometimes this pseudo is like the end of the Matrix movie, where Keanu Reeves can fly anywhere, transcending all the matrices.
3 Likes
I use Himaladin’s method in various apps. It works very well in most cases, except in edit forms. It seems like they don’t calculate columns “in advance” for edit forms only.
2 Likes
Also good to know. Good things to have in our toolbox.
1 Like
Can you please share an explanation of what it’s like? I don’t quite understand the case. Perhaps this will provide an opportunity to delve deeper.
I use it to block emails from being duplicated.
I set up a query in my Users table, pointing to the same Users table, filter by email is this row > email and rowID is not this row > rowID.
I have a hint component that tells people that there’s a duplicate and prevent submission based on your method, if that query is not empty.
It works in the add form, not the edit form.
So you check if there are duplicate emails that have already occurred in the user table, and prevent any further action to submit something?
Yep, in my case it was for admins who add new clients. They can not add new clients with an email that already exists in the Clients table.
1 Like
Alright. I’ll try it when I have some free time.
1 Like
Thanks a lot. I owe you so much for creating that method, I learned to use :has since that day.
1 Like
I got the answer. Is there any mistake?
@Jeff_Hager, @ThinhDinh, @Darren_Murphy
Obviously, you shouldn’t use a query to check for duplicate emails because the query value won’t change even if the email in the entry is already being changed.
Here, I use jointlist and JavaScript to extract the duplicate emails, then return them as a boolean value.
I also want to ask, does this duplicate email cause any issues in the application during sign-in?
1 Like
He’s inside of a Native Edit screen and going to restrict the submit button using css based on the visibility of hint component… so smart
1 Like