I would like to have the ability to tell the model to hide or disable a task when you do not have a row selected.
Now when you create a task that needs variables/values from a table you need to write a context to hide/disable the task when you do not have a row selected. This happens when you start with a empty table for example.
It will save time to just have to tell the model to disable/hide the task when you do not have a row selected.
In some instances you do want to be able to open the task (for example to create a record), but most tasks are related to the tab task parameters you enter.
+6- Warrior
Same for setting details to, for example, read-only in case no row is selected.
Same for reports
Same for add button in a detail, when no row is selected in the previous (main) document, which causes you not being able to add a row, because the PK/FK is not filled.
Right now we have to write code for such things, while some simple bits on each table could fix this (and the GUI interpretating it).
Would be a great value to our 'Low - Code' USP.
Same for reports
Same for add button in a detail, when no row is selected in the previous (main) document, which causes you not being able to add a row, because the PK/FK is not filled.
Right now we have to write code for such things, while some simple bits on each table could fix this (and the GUI interpretating it).
Would be a great value to our 'Low - Code' USP.
1 person likes this
+9Hello Michael,
For your information, the feature to disable (make read-only) a table task is scheduled for the 2020.1 release.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.