-
Currently, when creating a new record, it opens in a separate page after clicking the “New Record” button, and only one record can be added at a time. Is there a way to create a new row directly within the table view instead of opening a separate page?
-
When pasting data from Excel or Google Sheets into Bika, if there are not enough existing records, the additional data is not inserted. Is this the intended behavior?
-
In AITable, even when copying and pasting non-relational data, the platform automatically establishes links between related fields. However, Bika does not seem to support this behavior at the moment. Are there any plans to support this functionality in the future?
-
Currently, I can only delete fields one at a time. Is there a way to delete multiple fields at once?
-
I’m trying to move data from the “Master DB_Test” database to the “Master DB_move_Test” database. There are two records in total, and I want to move them individually. However, when I run the process, it duplicates one record instead of moving both. Could you please help identify what might be causing this issue? Please refer to the attached link for more details.
-
Lastly, could you please provide a proper manual or documentation for the automation features in Bika? It would be extremely helpful to have a clear guide.
Hi @Headchef.Yang , thanks for sharing all these thoughtful suggestions, I’ve passed your feedback along to our product and engineering team for review.
Regarding the specific issue you showed in your video, the problem is with the data path configuration inside the Loop — specifically in the two sub actions. Here’s how you can adjust it:
First, run a Test on the Loop step once.
Then, in the first Create Record action, set the field mappings to use the path:
current item/fields/xxxx (replace xxxx with your actual field name).
In the second Update Record action, set the record to:
current item/ID
Hope this helps!
Hi @Headchef.Yang ,
Thank you for taking the time to share such detailed feedback! Our product and engineering team has reviewed your suggestions. Below is some context and guidance for each point:
1. Creating new records directly in table view
Currently, Bika.ai requires creating a record by opening a separate pop-up window instead of adding a row directly in the table.
This method is designed to keep data entry more controlled and reduce errors. While some users found “quick create” convenient in the past, others complained that it was too easy to delete records, make mistakes, or cause data chaos. So we’re balancing the pros and cons.
For adding multiple records, you can use the Import or Incremental Import feature to create them in bulk.
Documentation: Import and Export | Bika.ai
2. Pasting more rows than existing records
If you paste data into a table with fewer records, new rows won’t be added automatically. Similar to point 1, this helps prevent accidental overwrites or unintended changes.
Again, we recommend using the Incremental Import feature for bulk additions.
3. Auto-linking relational fields when pasting
Bika doesn’t automatically link pasted data to related fields. In early designs, automatic linking sometimes caused confusion or unexpected changes. If needed, use the Bulk Update feature (in the top-right corner of the view) to update links in bulk.
This is another balance between ease of use and data stability.
4. Deleting multiple fields at once
Currently, you can only delete fields one by one. This helps avoid unintended changes to the data structure.
This is also a design choice to balance usability and data integrity.
5. Moving records between databases causes duplication
When moving records between databases, export the source data as a .bika file and import it into the target database. This avoids duplication and keeps data clean.
6. Automation documentation
Current automation docs are here: Triggers List | Bika.ai
If you have specific suggestions for what to add, feel free to share—we’ll consider them!
Thanks again for your feedback. Let us know if you need clarification on any points!
Thank you for your response.
When I try to export using Bika, I receive this message.
The linked database is already placed in the same folder, but this message still appears.
I would like to confirm whether the concept of “folder” mentioned here is different from what I understand as a folder.
This message indicates that the related tables referenced in your current export are not all located in the same folder you’re exporting from. There may be other related tables that are also not in the export folder.
Please check whether all the related tables needed for export are indeed within the folder you are exporting. Only when all related tables are in the same folder can the export proceed.
Note: Data source tables used by Magic Forms, Automations, Mirrors, and Dashboards must also be located in the same folder.
It’s already inside the same folder, but this message still appears.
@Headchef.Yang
Is the table with ID ‘dat6yji5HHh5d5ffyCUbK98d’ also in the current folder?
"Would it be possible to invite me to your Space Station to check this folder?
OK .
Can I have your email address?
@Headchef.Yang
My email address is：pengjin@vikadata.com
OK I’m done…
Hi @Headchef.Yang
I’ve already joined your space station, but I can’t see any resource information. Could you please grant me access to the file resources you need to export?
I’m done
Hi @Headchef.Yang
In your space station, I’m able to successfully export the Bika file from the PARA System folder. Please click the link below to view the operation video
Oh, thank you so much.
I see now that I need to download the entire folder.
I was trying to download just a single database, thinking it would work because it was part of the folder.
Now I understand what went wrong. Thank you again for the clarification.