Entity sets as cards on a canvas. Drag them where you want them, draw a link from a field on one to a field on the other, save it — and then test the whole join live against your own environment, with every hop reported pass or fail.
Pick the entity sets you care about and arrange them on a canvas. Drag, select, group — the picture on screen is the model you are building.
Connect a field on one entity to a field on another. That is the whole definition — no OData expression to get right, no expansion syntax to remember.
Press test and the join runs live on the environment you are connected to. Every hop comes back pass or fail, so a link that looks right but returns nothing is caught here, not in production.
Save a link set and DynBrowser's pages can use it to resolve one record to another — the configuration behind "which key on A finds the row in B".
This is the page a consultant or key user opens once to configure something, not a screen the shop floor needs. Permissions decide who may edit link definitions at all.
Relations are what you drew and what the test confirmed. There is no silent inference that works on your data and fails on someone else's.
Every hop of a join comes back pass or fail against your own tenant — before anyone depends on it.
Zero query syntax: a relation is a line between two fields, and that is the whole definition.
One place where entity relations are configured, instead of the same assumption hardcoded in several pages.
A demo takes thirty minutes and runs against your test environment — no installation required on your side.
Request a demo