توضیحات
Show Microsoft Dataverse records as lists and detail pages on your WordPress site, and write form submissions straight back into Dataverse.
تغییرات این نسخه
1.3.0
WBS Forms bridge: map a WBS Forms (or Contact Form 7-style) submission straight into a Dataverse table, with per-field typing (text, email, date, choice, multi-select choice, boolean, lookup, and lookup-by-name). Declare a mapping per form with the wbs_dataverse_connect_bridge_maps filter or the stored option. The form keeps rendering, validating and emailing on its own, so a Dataverse outage never loses a submission; the failure is logged and health-alerted.
Per-form connection: a bridge map can target a different Dataverse environment than the site default.
Top-level admin menu: Dataverse Connect now has its own menu item instead of living under Settings.
1.2.0
Extension hooks for add-ons; per-connection token and cache keys.
1.1.0
Health alerts: when a request to Dataverse fails, an email goes out right away to the alert address (and an optional second recipient), and again when the connection recovers. Failed form submissions always alert, whatever the cause.
Scheduled connection probe twice a day, so an expired client secret is reported within hours even on a quiet site instead of surfacing as broken forms weeks later.
Health status readout on the connection tab, and a wbs_dataverse_connect_health_event action for site-specific automation.
1.0.0
Initial release: collections (grid and detail shortcodes for any Dataverse table), write-back forms with field mapping and lookup binding, server-side Entra ID auth, response caching with fail-open behavior, them
WBS Forms bridge: map a WBS Forms (or Contact Form 7-style) submission straight into a Dataverse table, with per-field typing (text, email, date, choice, multi-select choice, boolean, lookup, and lookup-by-name). Declare a mapping per form with the wbs_dataverse_connect_bridge_maps filter or the stored option. The form keeps rendering, validating and emailing on its own, so a Dataverse outage never loses a submission; the failure is logged and health-alerted.
Per-form connection: a bridge map can target a different Dataverse environment than the site default.
Top-level admin menu: Dataverse Connect now has its own menu item instead of living under Settings.
1.2.0
Extension hooks for add-ons; per-connection token and cache keys.
1.1.0
Health alerts: when a request to Dataverse fails, an email goes out right away to the alert address (and an optional second recipient), and again when the connection recovers. Failed form submissions always alert, whatever the cause.
Scheduled connection probe twice a day, so an expired client secret is reported within hours even on a quiet site instead of surfacing as broken forms weeks later.
Health status readout on the connection tab, and a wbs_dataverse_connect_health_event action for site-specific automation.
1.0.0
Initial release: collections (grid and detail shortcodes for any Dataverse table), write-back forms with field mapping and lookup binding, server-side Entra ID auth, response caching with fail-open behavior, them