Feature 1
I would like to be able to include use a logical datatype in my engineering app
This would only be able to store two pre defined states - True/False, Yes/No , Petrol/Diesel etc
It would be visualised with either a check box or the state values as defined with a selection list.
This is more efficient than using a lookup table and rowlink for 2 state items where the state descriptions will never change.
In all other respects this datatype will behave like any other.
**What’s the problem that you’re looking to solve? I am building an engineering project tracking app where many data items have simple two state values for example -
Inspection Complete - YES
Is Item Faulty - YES
Is Item to be scrapped - NO
Is Remedial Work Required - YES
This will work well with simple mobile screens
Feature 2.
I would like to store file attachments to rows - i.e. upload local file system files to be stored in Honeycode in context with the app data.
I have done this in other systems using a datatype of Binary Large Object ( BLOB).
The file to attach is browsed for , and uploaded into the BLOB formatted field on the record.
File size limits would be imposed.
Any file type is suitable to be uploaded and attached.
The attachment is viewed by downloading and viewed using the local systems default viewer for that file type.
I would make extensive use of this for word documents, speadsheets, images , drawing files, pdf files etc
**What’s the problem that you’re looking to solve?
Engineering projects usually require Health and Safety Documentation , Specialist Drawings/ Diagrams , Specification Documents etc all of which should accompany the project workflow and be held in a central place for easy access and security. A Honeycode system would seem to be ideal to capture and store this information, and would be a huge benefit to the app.
I would like to be able to include use a logical datatype in my engineering app
This would only be able to store two pre defined states - True/False, Yes/No , Petrol/Diesel etc
It would be visualised with either a check box or the state values as defined with a selection list.
This is more efficient than using a lookup table and rowlink for 2 state items.
I would like to store attachments to records.
I have done this in other systems using a datatype of Binary Large Object ( BLOB).
The file to attach is browsed for , and uploaded into the BLOB formatted field on the record.
File size limits would be imposed.
Any file type is suitable to be uploaded and attached.
The attachment is viewed by downloading and viewed using the local systems default viewer for that file type.
I would make extensive use of this for word documents, speadsheets, images , drawing files, pdf files etc
I think this should be a feature request - we've asked for something similar, and this is a good description. I'd expand the first request a bit, and break it into two overlapping requests.
First, a simple logical type as described by Grabs, with a new standard screen checkbox object.
Second a field that's an enumeration type - it can contain one of a list of predefined values. Could be True/False, Yes/No/Maybe, or any arbitrary list of two or more items.
In addition to the values, it could have one or more matching lists of display attributes defined at design time - button text, fill color, font color and so on. For instance, petrol could display as green, diesel as yellow.
This implies a picklist that's similar to the HTML "<select>" tag in which the displayed text is separate from the returned value.
I'll pass on the input that both of you have provided for the feature requests of:
A logical or perhaps boolean data type object to indicate true / false, yes / no, etc.
Attachment support in Honeycode (perhaps as a BLOB format for a field in a row).
Mr-Bill, good additional thoughts too on a checkbox object and a different method to customize visual attributes. Our team has a few other similar requests around both of those ideas, so I will add your thoughts to those requests.
