Most of the times when adding a new entry, some of the fields are having the same value more than 80% of the time.
Could we have a predefined default value when a new form is created which could be changed if the user wants to.
This will make the app much more user-friendly.
The default value could be an option like the placeholder text in features.
This would help immensely.
I am thinking of having this as a field in the layout view.
Could be a small challenge to typecast the field to the datatype of the field.
Great idea. I suggest you add them to the feature request app.
Good idea with the placeholder. A checkbox could be added to make it the default value?
Yes that sounds perfect @Robert_Petitto
I think the default value is an indispensable feature nowadays; in my opinion there are much more advanced features than this already available in Glide but this one is so basic that, I believe, we can’t do without it anymore.
My clients ask me: “Why do I see the correct value in the field and always force me to rewrite it again?”
… and I never know what to answer!
You can already do this with a custom form, just saying…
But we do have default values in form entry components. Or am I misunderstanding what you are asking for?
@Darren_Murphy , @Jeff_Hager thanks for your attention.
I have not expressed myself correctly or I am missing something extremely obvious. I will explain better with an example.
Let’s say I have a custom form to insert an invoice row.
I will then have a choice component to select the item I am selling in that row; the following input fields are the quantity and the selling price.
The quantity is a variable datum and therefore must normally always be entered, while the selling price is a datum susceptible to variations.
How do I make the standard sale price appear pre-compiled in the input field?
Currently the only thing I can do is make the item’s selling price appear in the placeholder of the selling price input field.
If you tell me that I can do better you make me happy!
sorry for the bold text, it’s unintentional
You mean to say that the price value is dependent on the product which they choose in the choice component? Basically you want a lookup as a default value right?
Right. I’ve the lookup on the fly and I want to put that value in the input field, just like i am doing now with placeholder but I need a default value instead.
Seems quite simple - again if using a custom form with the input components writing to User Specific Columns.
- Create a relation between the selected product and the products list
- Use a lookup through that relation to get the product price
- Use a math column to calculate the total price based on the quantity selected
- Display the result of the math column in the form, and use it when the form is submitted with an Add Row action
I do 99% what you say, but I don’t need to calculate the price, I need to show the pre-filled typical price in the input field so that the user can confirm it or change it only when necessary.
How about an IF column that returns the user entered price…if not empty…else return the default price.
Display that IF column price on the screen, but if the user enters a price in an entry component, then the IF will kick in and instead display what the user entered. The IF value is what will be submitted through the form.
Yes indeed I have done so recently, but it is not the most elegant solution, in my opinion of course.
Haven’t tested this, but I imagine you could:
- Use the value of the product lookup as the default for the input component
- But have the target of the same component a User Specific column
Then use an if-then-else column to determine which value to use when Adding a row:
- If the User Specific column is empty (user has not overwritten the default), then use the lookup value
- Else use the User Specific column value
Yes, pretty much the same as @Jeff_Hager said.
That’s right, I am currently coming to the conclusion that it is not possible to do better than this.
Thank you all for your cooperation!