Hi @huydna @Thi_Nguyen @huyleminh ,
I am really happy, as this is the first modeling tool that introduced “Data Dependency (Lineage)” along with an ER Model. If you can find my previous comment, I always mentioned that this is the best feature of this modeling tool.
But because lineage comes with more challenges than a simple ERD, you guys need to work on these features too.
- Variable introduction is needed; more details are mentioned here: The missing part in lineage (dependency)
- Union needed: There are 3 ways to map source to target Lookup (which is already satisfied by the ERD); Second is CONTACT like Name is combination of FName, MName, LName which is also working as Dep{S.fName → T.Name \n S.LName → T.Name \n S.MName → T.Name}; But last part Union is missing; T.ID need all Data from S1.ID and S2.ID.
If possible, create a new line (different color, like pink this time, as blue is already used) for the union. As we are already using → for union => can be used. So Union identification will be easily highlighted.
Let me know your views.