Multi-environment schema mappings, a trial-expired dialog, and SSO fixes

Schema mappings are no longer one-size-fits-all per table, the trial-expiry experience is a real dialog instead of a silent failure, and SSO state catches up correctly after a refresh.

Multi-environment schema mappings

You can now map a DDB Toolbox schema per environment rather than once per table. If your dev, staging, and prod tables share a name but have schema differences (different versions, different entity sets), you can point each environment at the right schema and Dynomatic uses it automatically when you switch. This keeps schema-aware queries accurate across environments without juggling profiles.

Trial-expired dialog

When your trial expires, Dynomatic now shows a clear dialog explaining what happened, what’s still available, and how to upgrade. Previously this could fail quietly or leave you in an inconsistent state.

Other improvements

• SSO: the status popover no longer shows “expired” right after a successful token refresh — it now reflects the refreshed state immediately.