I have tried to create a vertabelo model using the "From Sql" file option , but for few tables it doesn't create all the columns.

I checked the sql file and the create table statement has all the columns

I have experienced a bug when trying to export my projects named like "WSI ćw. 7 zad. 1" to an image file.
I was getting the "500 Internal Server Error" consistently on multiple platforms, PCs, browsers and even shared users. I could export it to XML and re-import it correctly, but the image export remained bugged in the new file as well.
I have found out, that it was due to the name of the project. When changed to "WSIlab7ex1" it worked perfectly fine. I haven't found out precisely whether it was due to the special character "ć", the "." (dot) or the " " (space), but one these three is a culprit.
Hope, you'll at least some info to the error, as there's no feedback and it was blind luck permitting me to find out, what was the issue.

Love the platform BTW, great job guys!

Hi Team,

Can you advise on why i'm unable to log in to Vertabelo today using my google account?

Standard Audit Columns must be added, in the Physical Data Model, to every table in the data model.  These would include the usual -- CreateUserid, CreateTimestamp, UpdateUserid, UpdateTimestamp, LoadID, BatchID, etc. I avoid these in the LDM, as it's irrelevant to the documentation of business requirements.

With other tools I've used in the past, this was generally handled in a macro, or otherwise automated in some way. I don't see any way, in Vertabelo, to add a standard set of attributes/columns to more than one table at a time.  Is there such a feature?  For a large data model, this can be a significant amount of busy work.

I am using  

Thanks!

I KEEP GETTING THIS ERROR ON CHROME "Oops we've got a problem. Something went wrong" , I have re-installed Chrome and tried Chromium but in both it gives this problem..what do i do?

How come your generated 'DROP' DDL statements are not in the right sequence?  Constraints must be dropped first, then the tables. Child Table first, then Parent table. It should be intelligent enough to build the DDL correctly, based on hierarchy.