@ehabjy

Hi,

In Bubble, you don’t need to dynamically create new data types (tables) for each piece of equipment. Instead, you can simplify the structure by using fields to store relationships between your “Parent” and “Child” data types.

Here’s how you can do it:

  1. Parent Table (Equipment List): This table will include a list of equipment.

• Example fields: Equipment Name, Category, Other Attributes.

  1. Child Table (Equipment Details): This table will store the individual items related to each piece of equipment.

• Example fields: Item Name, Item Details, Related Equipment (this field will link back to the parent “Equipment” entry).

Instead of creating a new data type for every piece of equipment, you can link each piece of equipment to its details through a field called Related Equipment in the “Child Table”. When you add a new piece of equipment, you can create multiple related items automatically using workflows.

This setup scales well, even if you have thousands of pieces of equipment, and it keeps your database manageable. Bubble can easily handle this type of relational data structure without the need to create separate tables for each piece of equipment.

Hope this helps!