Wouldn't it be nice to have the ability to create conditional layouts based on self-written queries? Now you are forced to add expression fields with conditions and use them.
Closed
Conditional layout condition based on query
- Arjan Sollie
- Jeroen van den Belt
- Remco
- Dennis van Leeuwen
- Hugo Nienhuis
- Geurt
- eurban
- Pierius Lycklama A Nijeholt
- Freddy
- Peter Kruis
- Peter Jan Thierry
- Blommetje
- Selby Baidjnath
- tim
- Alban_T
- Martien Bakker
- Shawn Adrian Diño
- Maarten
- Anne Vries
- MtHoen
- Allard Lakerveld
- Marco Maat
- Remco Duijsens
- Marius Korff
- Guido Bijl
- najambia
- Timothy Mentowidjojo
- rbiram
- Tristan
- Raymond Gerritsen
- Eric
- jligtvoet
- Eric F
- Max Ferket
- Corstiaan Kamp
+23Updated idea statusNew→Open
"Wake me up before you low-code" | On holiday 06-02 till 27-06
+1- Vanguard
- 18 replies
Is there a update on this idea?
- 678 replies
After careful consideration we have decided to close this idea, as it has limited added functional value compared to using expression fields.
- Apprentice
- 6 replies
Jasper wrote:
After careful consideration we have decided to close this idea, as it has limited added functional value compared to using expression fields.
Too bad, it would have made life a bit more easy and more consequent.
+6- Captain
- 63 replies
Jasper wrote:
After careful consideration we have decided to close this idea, as it has limited added functional value compared to using expression fields.
I prefer not to pollute my data model with expression fields, especially when that expression fields sole purpose would be for a conditional layout. To me it makes more sense to place this expression in the conditional layout instead of the table.
+16Marius Korff wrote:
Jasper wrote:
After careful consideration we have decided to close this idea, as it has limited added functional value compared to using expression fields.
I prefer not to pollute my data model with expression fields, especially when that expression fields sole purpose would be for a conditional layout. To me it makes more sense to place this expression in the conditional layout instead of the table.
Even better would it be if expression fields (the code) would move to functionality and you can then link the result to a expression field on a table or to a conditional layout.
There would be many benefits.. including using TVF's. to populate 2 expression fields..
+23Hey
We're always open for ideas certainly. We are continuously improving the platform in all aspects. Moving expressions and calculated fields to Functionality is something I never thought of to be honest.
In regards to being able to review expression fields, or any code, we want to move towards a Pull request style merge session where you can review all the actions with preferably live updates/data. As you can imagine, it's not as easy as adding a checkbox with Approved.
On the 18th of April during the Developer event, Jasper will share the Roadmap and tell you all about the upcoming additions to the platform. Universal GUI is reaching its feature parity and we are closing in on bringing everyone new awesome features.
+16Mark Jongeling wrote:
Hey
We're always open for ideas certainly. We are continuously improving the platform in all aspects. Moving expressions and calculated fields to Functionality is something I never thought of to be honest.
In regards to being able to review expression fields, or any code, we want to move towards a Pull request style merge session where you can review all the actions with preferably live updates/data. As you can imagine, it's not as easy as adding a checkbox with Approved.
On the 18th of April during the Developer event, Jasper will share the Roadmap and tell you all about the upcoming additions to the platform. Universal GUI is reaching its feature parity and we are closing in on bringing everyone new awesome features.
Well I hope then that the event will be recorded, I will not be in the Netherlands on that day.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.