Skip to main content

Idea pipeline (top 25)

Filter by idea status

Filter by product

1967 Ideas

K.Bakkenes
Captain
K.BakkenesCaptain

Validate field input value without using a default/layout/triggerCompleted

If we want to check a field on a valid input value (and prevent saving) we need to create a default, a layout and a trigger procedure.We regularly use a combination of a default + trigger because the user will see an error message as early as possible and the trigger would prevent the insert the record.The default will validate the field after leaving it (@cursor_from_col_id) and return an error message. The trigger will also validate the field with the same code (but with the inserted of course).There’s a problem with this combination when a user fills in the field and saves the form without leaving the field first. In this case the error message (see screenshot below) will be shown twice. Once for the default and once for the trigger. A solution could be to add a layout procedure that also validates the field with (again) the same code. The layout procedure could disable the save button when it determines that the field value is incorrect. But this result in a default, layout and a trigger with the same validation check. Not exactly low code.What if the TSF offers a field validation option? A screen to create one or multiple validations per field. It could range from simple checks like: field is empty, field value must be unequal to 0 or the option the add a query. We could also add a desired result to a configured field validation like showing an error message or placing a conditional layout.These new field validations need to be executed in the GUI before saving/inserting a record and could act as a default because the validation is linked to a field.  They can also be used for dynamically creating the validation within triggers.

Multiple instances of the TSF databaseCompleted

We are running a development platform with about 30 developers and thus we are often bothered with a slow working SF, which primarily happens when someone is either generating definitions,validating definitions or executing a merge. But it also can happen sometimes just by trying to save a template or a new table column.The root cause of this, in my opinion, is the fact that all of our transactions within the SF are executed on one single SF database. Especially during generation or merging a lot of data is being read, deleted or created in that single database, which often results in a slow performance or even processes being assigned as deadlock victim.I believe the performance of the SF could largely be improved if we were able to run multiple instances of the SF database, maybe even across multiple database servers, and be able to merge branches from different databases. A couple of great benefits are:Whenever I work in a branch I am only bothering people that work in the same branch as I do or at least people that work in the same SF database that I do. It greatly improves scalability, especially when it supports multiple database serversEspecially the first benefit is great for a performance improvement.With about 30 people developing there are several merges happening in a week. Consider the trunk to have it’s own SF-database and executing a merge to the trunk. This merge will then primarily lock access to the SF-database that belongs to the trunk and not slow down performance of the other 29 developers still developing in their own branches.