Welcome to the Alloy Ideas Portal đź‘‹ Here, you'll be able to browse improvement ideas raised by our community, vote on ideas you agree with or even raise your own ideas. We review all ideas raised and we endeavour to respond to all raised ideas.
Any ideas submitted will be immediately visible on the portal for others to vote on, please do not include anything in your ideas you do not wish to be shared with others.
The ability to generate an overall entity diagram of ALL tables, at the moment you can explore the selected table and see what is joined to it, or look at it through the navigator to go from table to table. or look at it from the graph view
But it would be nice to see something like Micrsoft Acess and other systems have, where all the tables and all of the links are shown on one screen/pdf.
In reality tables have links upon links upon links that are hard to visualise.
Or the more traditional UML diagram, which is near enough the same.
So the layman can see what's going on under the hood, rather than looking at each table in turn to try and work it out.
Hi! Thanks for submitting this idea. Due to the unique way data is stored in Alloy and the flexibility allowed within the data structure, it may not be possible to display a standard ERD for all designs and design interfaces as this would differ between Alloy customers. We may in the future investigate a visualiser that could build an ERD from a single design and show parents and children designs recursively. If you wanted to gain access to the design information for all designs, there is a list endpoint on the Alloy API that will provide this data.
Hi. yes there will be many tables that have no links or parents/children or lookups. and ys each customer will be very different, and this would be a useful tool to enable an overview of how all the designs relate or not.
I can see it via swagger, and go through each design and see what it is linked to,
It could be a simple visualiser in the form of a report.
SO without having to go through every design to find out whats going on in the entire database, it scans through and flags them as "has no links", has parents only", "has clildren only", "has both"
Even that would be a major step to understanding the whole database in its entirety, rather than looking at the design/ design interface level.
And an Entity diagram for permissions, as sometimes it is hard to work out where an inherited permission has come from, from the design, from the interface, from a role, from a group. or is that another idea altogether