If not, I think this would be very useful! You could guide it with your main objects and let it traverse
2 Likes
Isn’t this basicly the idea behind Workflow builder, or am I misunderstanding what you mean?
Hi @mellerbeck,
You are right, there isn’t a direct functionality in Solution Designer to traverse between objects. This is something that we can look at adding.
Today, as @ecitaku pointed out, Workflow builder would be the best place to traverse through your ontology if you are looking for a graphical representation of your existing ontology. Alternatively, you can also load a saved data lineage graph with your ontology representation into SD for further editing.
1 Like
I interpret @mellerbeck ’s request as a way to simplify / validate documentation in SD.
We frequently use SD in the planning phase to detail out and discuss a pipeline architecture or workshop module flow (embedded modules and interfaces).
once going into development, reality kicks in and you sometimes divert from your plan and you might forget to updating docs. I think it would be helpful to have a simple way to load (just like in data/workflow lineage) the parent/child nodes of ann RID. Basically to retrospectively add the actual architecture into SD and adjust the documentation again. Hope that makes sense 
Yes, make the solutions design match what actually is built
I do think the path from data lineage → solutions designer is viable. But it is a hoop to jump through.