App and screen level variables
Hariprasad
App and screen variables are mostly needed and useful features to store or assign values based where data can be accessed.
For example variables will be more useful at calculator kind of applications. Also these variable should be accessable for formulas to store return values of formaulas.
z
zethbaker
Variables screen level would be amazing to have! I am tired of add an input field to store “variable data” it should be an easy add.
C
Conor
This might be similar to the states request depending on how they would implement state.(https://adalo.canny.io/feature-requests/p/states)
If in theory they created state per screen as a way to store generic variables or nested variable for json objects, then it would probably serve both these purposes. If the objects are linked to the state and can successfully trigger re-render then that in theory would mean the state data could be used in magic text or formulas.
This would add the extra requirement of an app level state but could be an option to combine asks depending on engineering implementation specifics.
Josh Johnson
Josh Johnson
Merged in a post:
Use Variables, Functions and Math on page
Geoff Thomas
One of the biggest features that I am missing in Adalo is the ability to do math more than just a very basic level. This limits the functionality I can build into the apps I create here. I love the interface for quick layouts and testing, but to create handy applications that are of actual value, I would need to be able to do some more sophisticated functions.
So for example:
Supposed I am paid on commission and there are multiple elements to me being paid if I hit various performance criteria.
So lets say I get paid $100 per sale and then bonuses as follows:
5 sales: $200
9 sales: $500
12 sales: $1000
14 sales: $1500
and for every sale above 15 add an extra $100 to $1500.
The way I would do this in excel (which may not be the best way) is a nested if function. The only way I can figure to do it in Adalo right now is to make hidden functions for every options, and only display them if true. This creates massive redundancy and is really arduous to change if the pay plan were to change.
So another things that would be super helpful in developing apps is being able to calculate something once on the page and then being able to recall it somewhere else on the page so I can use that again. A variable that is stored for calculation purposes. This would be different from the manual data, which can't be calculated dynamically as far as I can tell.
In the pay app, imagine the output
Sales: 10
Pay from sales: $1000
Pay from sales units: $500
Then I would want to calculate total pay, which would just be $1000+ $500, but right now, I have to redo all the calculations to get this to show.
I understand that building out complete no code math functions that can do everything is an almost infinite job, but I am not asking for that. What is needed is just some added functionality, so that we can make basic math work harder for us in the app.
Additionally, having some way to store calculated results in the database could be helpful as well.
Basoene Oruye
I have run into this need countless times
Gabriel Schemoul
This is a must have. I don't understand why this feature hasn't been developed yet.