Skip to main content
Simon D101
March 24, 2023
Solved

Importing ERD file from MySQL leads to error "Error:We couldn't parse the output you provided." in Lucidchart

  • March 24, 2023
  • 26 replies
  • 903 views

Hi

I've created an ERD on LucidChart and exported it for MySQL and tried to use this input to re-create in LucidChart the same document with the ERD import from SQL but get an error.
"Error:We couldn't parse the output you provided."
What is wrong with my input?

I'm trying to figure out how should I setup my SQL schema for import from SQL

How can generated data from export not being good for input?

Thank you

Best answer by Micah

Hi @efredericksen, thanks for this question! Can you confirm what DBMS you’re using and that you’ve selected the corresponding query in this modal?

I see “sqlserver” in your output. If this is correct, I recommend comparing it to the example output file I’ve attached to this comment. Using this as a template will allow you to identify any differences in structure that Lucidchart isn’t able to interpret. 

 

 

Comments

April 2, 2024

hI @Micah ,
Below is the CSV i have tried.

dbms,TABLE_CATALOG,TABLE_SCHEMA,TABLE_NAME,COLUMN_NAME,ORDINAL_POSITION,DATA_TYPE,CHARACTER_MAXIMUM_LENGTH,CONSTRAINT_TYPE,TABLE_SCHEMA,TABLE_NAME,COLUMN_NAME
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJ_ELEMENTS_B,PROJ_ELEMENT_ID,1,int,NULL,PRIMARY KEY,,,
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJ_ELEMENTS_B,PROJECT_ID,6,int,NULL,FOREIGN KEY,Sales,PJF_PROJECTS_ALL_B,PROJECT_ID
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,PROJECT_ID,1,int,NULL,PRIMARY KEY,,,
 

Micah
Lucid community team
April 3, 2024

@ACDC I’m sorry for the continued trouble here. I tested your CSV and was able to add tables to my canvas with relationship lines automatically created. In my example below, I added two of each table and see the following:

 

 

Can you try pasting your CSV as plain text in the upload option, add the tables to the canvas, and if no relationship lines are drawn, respond with a screenshot of what you’re seeing?

 

April 4, 2024

 hi @Micah , That worked for me..However when i add more tables (as i want to expand it ) and realtionships it just does not pick up the relationships… Below is the CSV , see if you can spot a problem…

dbms,TABLE_CATALOG,TABLE_SCHEMA,TABLE_NAME,COLUMN_NAME,ORDINAL_POSITION,DATA_TYPE,CHARACTER_MAXIMUM_LENGTH,CONSTRAINT_TYPE,TABLE_SCHEMA,TABLE_NAME,COLUMN_NAME
sqlserver,AdventureWorks2008R3,Sales,PJB_BILLING_EVENTS,EVENT_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJB_BILLING_EVENTS,PROJECT_ID,11,int,NULL,FOREIGN KEY,Sales,PJF_PROJECTS_ALL_B,PROJECT_ID
sqlserver,AdventureWorks2008R3,Sales,PJB_BILLING_EVENTS,TASK_ID,12,int,NULL,FOREIGN KEY,Sales,PJF_PROJ_ELEMENTS_B,TASK_ID
sqlserver,AdventureWorks2008R3,Sales,PJB_INV_LINE_DISTS,INVOICE_DIST_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJB_INV_LINE_DISTS,INVOICE_ID,4,int,NULL,FOREIGN KEY,Sales,PJB_INVOICE_HEADERS,INVOICE_ID
sqlserver,AdventureWorks2008R3,Sales,PJB_INV_LINE_DISTS,INVOICE_LINE_ID,5,int,NULL,FOREIGN KEY,Sales,PJB_INVOICE_LINES,INVOICE_LINE_ID
sqlserver,AdventureWorks2008R3,Sales,PJB_INV_LINE_DISTS,BILL_TRX_ID,7,int,NULL,FOREIGN KEY,Sales,PJB_BILL_TRXS,BILL_TRX_ID
sqlserver,AdventureWorks2008R3,Sales,PJB_INV_LINE_DISTS,CREDITED_INVOICE_ID,76,int,NULL,FOREIGN KEY,Sales,PJB_INVOICE_HEADERS,CREDITED_INVOICE_ID
sqlserver,AdventureWorks2008R3,Sales,PJB_INV_LINE_DISTS,CREDITED_INVOICE_LINE_ID,77,int,NULL,FOREIGN KEY,Sales,PJB_INVOICE_LINES,CREDITED_INVOICE_LINE_ID
sqlserver,AdventureWorks2008R3,Sales,PJB_INV_LINE_DISTS,RBS_ELEMENT_ID,82,int,NULL,FOREIGN KEY,Sales,PJF_RBS_ELEMENTS,RBS_ELEMENT_ID
sqlserver,AdventureWorks2008R3,Sales,PJB_INVOICE_FORMATS,INVOICE_FORMAT_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJB_INVOICE_FORMATS,INVOICE_GROUP_ID,3,int,NULL,FOREIGN KEY,Sales,PJB_INV_GROUP_HEADERS,INVOICE_GROUP_ID
sqlserver,AdventureWorks2008R3,Sales,PJB_INVOICE_HEADERS,INVOICE_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJB_INVOICE_HEADERS,ACCTD_RATE_TYPE,36,varchar,NULL,FOREIGN KEY,Sales,GL_DAILY_CONVERSION_TYPES,ACCTD_RATE_TYPE
sqlserver,AdventureWorks2008R3,Sales,PJB_INVOICE_LINES,INVOICE_LINE_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJB_INVOICE_LINES,INVOICE_ID,5,int,NULL,FOREIGN KEY,Sales,PJB_INVOICE_HEADERS,INVOICE_ID
sqlserver,AdventureWorks2008R3,Sales,PJB_INVOICE_LINES,CREDITED_INVOICE_ID,11,int,NULL,FOREIGN KEY,Sales,PJB_INVOICE_HEADERS,CREDITED_INVOICE_ID
sqlserver,AdventureWorks2008R3,Sales,PJB_INVOICE_LINES,INVOICE_FORMAT_ID,14,int,NULL,FOREIGN KEY,Sales,PJB_INVOICE_FORMATS,INVOICE_FORMAT_ID
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJ_ELEMENTS_B,PROJ_ELEMENT_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJ_ELEMENTS_B,PARENT_STRUCTURE_ID,2,int,NULL,NULL,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJ_ELEMENTS_B,PROJECT_ID,6,int,NULL,FOREIGN KEY,Sales,PJF_PROJECTS_ALL_B,PROJECT_ID
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,PROJECT_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,PROJECT_TYPE_ID,2,int,NULL,FOREIGN KEY,Sales,PJF_PROJECT_TYPES_B,PROJECT_TYPE_ID
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,CARRYING_OUT_ORGANIZATION_ID,3,int,NULL,NULL,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,PUBLIC_SECTOR_FLAG,4,varchar,NULL,NULL,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,PROJECT_STATUS_CODE,5,varchar,NULL,FOREIGN KEY,Sales,PJF_PROJECT_STATUSES_B,PROJECT_STATUS_CODE
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,COST_IND_RATE_SCH_ID,6,int,NULL,FOREIGN KEY,Sales,PJF_IND_RATE_SCH_B,COST_IND_RATE_SCH_ID
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,COST_IND_SCH_FIXED_DATE,7,date,NULL,NULL,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,OVR_COST_IND_RATE_SCH_ID,8,int,NULL,FOREIGN KEY,Sales,PJF_IND_RATE_SCH_B,OVR_COST_IND_RATE_SCH_ID
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,LABOR_TP_SCHEDULE_ID,9,int,NULL,FOREIGN KEY,Sales,PJF_TP_SCHEDULES,LABOR_TP_SCHEDULE_ID
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,LABOR_TP_FIXED_DATE,10,date,NULL,NULL,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,CC_PROCESS_NL_FLAG,11,varchar,NULL,NULL,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,NL_TP_SCHEDULE_ID,12,int,NULL,FOREIGN KEY,Sales,PJF_TP_SCHEDULES,NL_TP_SCHEDULE_ID
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,NL_TP_FIXED_DATE,13,date,NULL,NULL,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,WORK_TYPE_ID,14,int,NULL,FOREIGN KEY,Sales,PJF_WORK_TYPES_B,WORK_TYPE_ID
sqlserver,AdventureWorks2008R3,Sales,PJF_PROJECTS_ALL_B,CINT_RATE_SCH_ID,15,int,NULL,FOREIGN KEY,Sales,PJC_CINT_RATE_SCH_B,CINT_RATE_SCH_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PLAN_LINE_DETAILS,PLAN_LINE_DETAIL_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJO_PLAN_LINE_DETAILS,PLANNING_ELEMENT_ID,8,int,NULL,FOREIGN KEY,Sales,PJO_PLANNING_ELEMENTS,PLANNING_ELEMENT_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PLAN_LINE_DETAILS,PLAN_VERSION_ID,13,int,NULL,FOREIGN KEY,Sales,PJO_PLAN_VERSIONS_B,PLAN_VERSION_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PLAN_LINES,PLAN_LINE_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJO_PLAN_LINES,PLANNING_ELEMENT_ID,39,int,NULL,FOREIGN KEY,Sales,PJO_PLANNING_ELEMENTS,PLANNING_ELEMENT_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PLAN_LINES,PLAN_VERSION_ID,41,int,NULL,FOREIGN KEY,Sales,PJO_PLAN_VERSIONS_B,PLAN_VERSION_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PLAN_TYPES_B,PLAN_TYPE_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJO_PLAN_VERSIONS_B,PLAN_VERSION_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJO_PLAN_VERSIONS_B,PROJECT_ID,16,int,NULL,FOREIGN KEY,Sales,PJF_PROJECTS_ALL_B,PROJECT_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PLAN_VERSIONS_B,PLAN_TYPE_ID,18,int,NULL,FOREIGN KEY,Sales,PJO_PLAN_TYPES_B,PLAN_TYPE_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PLANNING_CURRENCIES,PLANNING_CURRENCY_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJO_PLANNING_CURRENCIES,PLANNING_OPTION_ID,2,int,NULL,FOREIGN KEY,Sales,PJO_PLANNING_OPTIONS,PLANNING_OPTION_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PLANNING_ELEMENTS,PLANNING_ELEMENT_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJO_PLANNING_ELEMENTS,PLAN_VERSION_ID,6,int,NULL,FOREIGN KEY,Sales,PJO_PLAN_VERSIONS_B,PLAN_VERSION_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PLANNING_ELEMENTS,PROJECT_ID,7,int,NULL,FOREIGN KEY,Sales,PJF_PROJECTS_ALL_B,PROJECT_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PLANNING_ELEMENTS,TASK_ID,8,int,NULL,FOREIGN KEY,Sales,PJF_PROJ_ELEMENTS_B,TASK_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PLANNING_ELEMENTS,RBS_ELEMENT_ID,9,int,NULL,FOREIGN KEY,Sales,PJF_RBS_ELEMENTS,RBS_ELEMENT_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PLANNING_OPTIONS,PLANNING_OPTION_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJO_PLANNING_OPTIONS,PLAN_TYPE_ID,31,int,NULL,FOREIGN KEY,Sales,PJO_PLAN_TYPES_B,PLAN_TYPE_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PLANNING_OPTIONS,AMOUNT_SET_ID,42,int,NULL,FOREIGN KEY,Sales,PJO_FIN_PLAN_AMT_SETS,AMOUNT_SET_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PROJECT_PROGRESS,PROJECT_PROGRESS_ID,1,int,NULL,PRIMARY KEY,NULL,NULL,NULL
sqlserver,AdventureWorks2008R3,Sales,PJO_PROJECT_PROGRESS,PROJECT_ID,2,int,NULL,FOREIGN KEY,Sales,PJF_PROJECTS_ALL_B,PROJECT_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PROJECT_PROGRESS,PROJ_ELEMENT_ID,5,int,NULL,FOREIGN KEY,Sales,PJF_PROJ_ELEMENTS_B,PROJ_ELEMENT_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PROJECT_PROGRESS,ELEMENT_VERSION_ID,6,int,NULL,FOREIGN KEY,Sales,PJF_PROJ_ELEMENT_VERSION,ELEMENT_VERSION_ID
sqlserver,AdventureWorks2008R3,Sales,PJO_PROJECT_PROGRESS,PLAN_VERSION_ID,10,int,NULL,FOREIGN KEY,Sales,PJO_PLAN_VERSIONS_B,PLAN_VERSION_ID
 

Micah
Lucid community team
April 4, 2024

Hi @ACDC, thanks for your response. I’ve uploaded your CSV to import tables, and when experimenting by dragging a few out, I was able to see automatically-created relationships between Sales.PJO_PLAN_VERSIONS_B and many other tables. Take a look below:

 

Are there any relationships in particular that you are expecting to see and are not?

April 5, 2024

@Micah ,  i wonder if this is happening to me because i am on trial not fully signe dup yet..

 

Micah
Lucid community team
April 8, 2024

@ACDC Your trial period gives you full access to all features, so that shouldn’t be the cause of the problem. I am so sorry this is persisting! Can you clarify if you don’t see what I’ve shown in my screenshot above? Are there specific relationships you’re expecting to see that aren’t appearing?