How to change from role when synchronizing to class diagram?

Hey guys.

I am using Visual Paradigm Enterprise 18.1 Evaluation Version and want to visualize a database as a uml class diagram. For that I used “Reverse DDL” to generate an ERD and then “Synchronize to Class Diagram” to obtain a Class Diagram.

The problem is that it is not usable to understand how the tables are connected since the foreign keys are not displayed anymore. I noticed that the “to role” contains the name of the table and the “from role” the foreign key with “_Id” removed. Now I have associations with the exact table names written at the ends. Honestly it does not make any sense that those labels are added. If anything they should be switched.

I looked forever but couldn’t find a way to change the assignments of the labels. How can I display the foreign key? I don’t care if it is in the caption, the “from” or the “to node” , it just needs to be set automatically.

My second question is if there is a merge functionality for class diagrams. What I mean is that if my database is expanded and I have to convert it into a class diagram again it is way too much work to sort it again. Is there a merge that adds all the new tables and connections to an already existing diagram without destroying the previous structure?

Doing both tasks manually is not possible since the database has 50 tables. It would be possible for one time but since it has to be redone regularily it should be set automatically.

Thanks in advance.

Kind regards!

Interesting problem — I’ve hit this same awkwardness reverse-engineering legacy schemas. One thing worth separating out before chasing the role-label setting: are you treating the class diagram as a one-time documentation snapshot, or do you actually need it to stay in sync as the database keeps changing?

If it’s the latter, I’d think twice about resyncing 50 tables by hand every time — that’s less a “how do I rename this label” problem and more a “which model is the source of truth” problem. A lot of teams end up flipping the direction: model the domain in the class diagram first, generate the DDL forward, and only reverse-engineer once to bootstrap. Curious whether that’s an option for you here, or whether the database is owned by another team and you’re stuck reverse-syncing no matter what.