Skip to main content
Nov 16, 2026 9:41 AM UTC
Idea

Imported Tables

After importing a set of tables from a database/data source.  If you close the diagram and then reopen it, why is it so incredibly difficult to find those tables?  
The frustrating bit is that Lucid typically treats imported tables as objects on the canvas, not as a separate persistent catalog you can browse later. Once imported, there often isn't a dedicated "Imported Tables" list showing everything that exists in the model but isn't currently visible on the diagram.  What is VERY frustrating is that these are neither Layers or Shapes, they are entities and the system should recognise as such.

What I’m describing highlights a mismatch between the user's mental model and Lucid's implementation model. From my perspective, I've imported a database schema. At that point Lucid knows:

  • These are entities/tables
  • Their names
  • Columns
  • Keys
  • Relationships
  • Source database

They should be made available at least via the ‘View’ menu option.

Comments

kmougammadou
Nov 16, 2026 2:29 PM UTC

Hi ​@Kevin.Plunkett, thanks for your post in the community! 

When you import a database schema using the ERD import feature, Lucidchart actually saves all of your imported databases, schemas, and tables directly inside your Shape menu on the left side of the editor—so you do not have to rely solely on what is already placed on the canvas. 

Here is how you can locate and reuse your imported tables after reopening a document:

  1. Open the Shape menu on the left side of the canvas. Each imported database appears as its own collapsible section.
  2. Click to expand your database section (and any schema subsections inside it) to view the full list of imported tables. From there, you can drag and drop any table onto the canvas at any time.
  3. Optional: If you do not see your database sections in the left panel, open the Shape Library Manager (by clicking More shapes at the bottom of the shape menu in the classic editor, or searching in the left panel) and make sure the Entity Relationship shape library is enabled.
  4. If your database changes, you can import an updated database file at any time to update the fields both in your Shape menu and on the canvas.

For full details on importing, managing, and updating database schemas, please review our Create an Entity Relationship Diagram in Lucidchart article.

Please let me know if you have any additional questions or concerns.

Translate
Nov 17, 2026 8:19 AM UTC

Thank you for such a prompt response.  I did eventually discover this is where they hide but to me and other Lucid users in our DE group, this simply is not logical.  My point still stands, the imported database tables are NOT shapes, they are data entities in their own right and therefore should be considered as such.

Translate
kmougammadou
Nov 18, 2026 1:32 PM UTC

Hi ​@Kevin.Plunkett, Thanks for your response! We’re very interested in your feedback and committed to continually improving our products. If you’re willing to share, we’d love to hear more details about your use case or what you’d like to see in this experience within this thread. I’ve also converted this post to an idea so that it’s visible to others within the Product Feedback section of the community - from here, they can upvote it and add details of their own.

Finally, for more information on how Lucid manages feedback via this community, take a look at this post:

What happens to my feedback? | Community

Translate
Nov 19, 2026 8:13 AM UTC

Thank you.  I am only one member of a Data Engineering team, we use Lucid extensively and just occasionally we find things that ‘annoy’ us.

Translate