A field is a vertical data column in a database, similar to the header column of an Excel table. Each field stores specific types of information.
Bika.ai supports over 20 field types for different scenarios:
More details: Help Center - Fields
The newly created database will come with three basic fields as examples. You can delete them or change the field types, or directly add new fields.
For field operations, Bika.ai provides two different interaction path methods, and there will be slight differences in application scenarios and logical effects between the two.
The first one is that you can operate directly on the grid view interface. Click the "..." in the column header to enter the "field editor" interface. You can also click the "+" button to quickly add a new field. This method is suitable for scenarios where there are a small number of fields to operate.
The second one is that you can click the "..." button in the upper right corner of the database interface to enter the database editor. Perform various complex and batch field configurations in the database editor.
You can click the "+" button on the far right of the database header to create a new field. You can also click the "..." in the upper right corner of the interface to enter the database editor and then add. The difference between the two:
Difference | Who can operate? | Will the field appear in other views? |
Create field from view header | Members with "Can manage" permission for the database |
|
Create field from database editor | Members with "Can manage" permission for the database |
|
Fill in information in the popped-up field editing interface.
Click the "Save" button at the bottom to complete the configuration of the field.
Modify existing fields anytime:
Quick edit: Double-click the column header
Full edit: Hover over the field title → Click ... → Edit
Open the editing panel to modify, and it will take effect after saving.
Remove unneeded fields (except first filed):
The display or hiding settings of fields are very flexible. You can assign different display or hiding states to the same field under different views to meet the needs of different scenarios.
When you read a database and conduct data analysis, if there are too many displayed fields, it may affect the reading experience. At this time, you can quickly temporarily hide the fields that you do not currently need to view through the "Hide Field" control on the view toolbar.
This way of hiding operations is only effective for you. When other members in the space access the same view, they can still view this field normally.
Creating multiple views is to recombine and display the data of a database through different filtering conditions and interaction forms, so as to improve the reading experience and work efficiency of members in different business scenarios.
Members with "Can manage" permissions for the database can enter the view editing interface of the database and then perform batch hiding or showing operations on fields. The display or hiding operations in this way take effect for all members of the space. Any member accessing the same view of the database will see exactly the same rows and columns initially.
For example, if a member with "Can manage" permission sets field A to "Hidden" in the view editing interface. Then all members entering this view, whether in the data area or the "Hide field" control on the view toolbar, will not be able to see field A.
View editor vs View toolbar
Difference | Effect | Who can operate |
Hide fields in view editor |
|
|
Hide fields in view toolbar |
|
|
Q: If field A is set as "required", and this field is in a hidden state under view X. Will the required field verification take effect when creating a record? A: It will not take effect. The system follows the verification trigger mechanism of "what you see is what you verify", and it only takes effect when the field is visible. For example, if the "alternate email" field is hidden in the "customer view", even if this field is marked as required, the user will not trigger verification when submitting the form in this view.
In the following special cases, the required field verification will not take effect:
