Page 1 of 1

Custom Fields Rather Than Custom Tables

Posted: Mon Oct 17, 2016 12:21 am
by robinwilson16
Sometimes we want to add a single custom field to a screen.

Unfortunately tables do not have custom fields in them so it means a whole new sub-section needs to be added to a screen with a new button, enabling the custom row in the database table to be added which takes up a lot of room and adds complexity to the screen as well as the amount of screen space it takes up. It also means this custom field cannot be made mandatory and we cannot enforce users only record it once as there is nothing stopping them adding multiple new rows.

I would like Capita to support adding custom fields to existing tables then a screen could just have a single additional input field rather than all the controls that must be added for custom entities and later data clean-up exercises.