Custom Fields Rather Than Custom Tables

A forum to post features you wish UNIT-e had in the hope they may be added in future
Post Reply

Vote for this?

No votes
Total votes: 2

User avatar
Site Admin
Posts: 185
Joined: Sun Oct 16, 2016 6:46 pm
Forename: Robin
Surname: Wilson
College Name: FEA
Position: MIS Consultant
LinkedIn Profile:

Custom Fields Rather Than Custom Tables

Post by robinwilson16 » Mon Oct 17, 2016 12:21 am

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.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest