WBS Connect for Dataverse
| 开发者 | ztwoods |
|---|---|
| 更新时间 | 2026年7月27日 20:18 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Collections. Publish any Dataverse table by naming the table, the columns and an optional status filter. No code required; developers can also register collections via a filter.
- Grid and detail on one page.
[wbsdvc_collection]renders the card grid, and the same page renders the detail view when a record is selected, so links stay short. - Clean detail URLs. Point a collection at a slug column and detail links use readable slugs (
?dvc=my-record) instead of raw record ids. Id links keep working as a fallback. - Write-back forms. Map form fields to columns of any table; submissions create records in Dataverse, optionally related to the record the form was shown on. Every submission is nonce-verified, honeypot-checked and rate limited.
- Server-side authentication. The plugin signs in with an Entra ID app registration (client-credentials flow) and a Dataverse application user with a least-privilege role. Credentials never reach the browser;
wp-config.phpconstants are the recommended home for them. - Caching and fail-open. Reads are cached with a configurable TTL. When Dataverse is unreachable, pages show a friendly notice instead of failing; the site never goes blank.
- Display-ready values. Choices, money, dates and lookups arrive formatted by Dataverse itself, in the environment's locale.
- Themeable. All output runs through templates a theme can override, so markup, classes and SEO belong to the site owner.
- PHP 8.0 or newer, WordPress 6.0 or newer.
- Access to a working Microsoft Dataverse or Dynamics 365 environment is required. Without one the plugin has no function. Free developer environments are available from Microsoft: https://learn.microsoft.com/power-platform/developer/plan
- Microsoft Entra ID token endpoint (
login.microsoftonline.com). The plugin requests OAuth2 access tokens here using the tenant id, client id and client secret you configure. This happens whenever a cached token has expired. - Your Microsoft Dataverse environment (the
*.dynamics.comURL you configure, for examplehttps://yourorg.crm4.dynamics.com). The plugin reads the records you chose to publish and creates the records your visitors submit through configured forms (typically a name, email address, phone number and message). This happens on page views of pages using the shortcodes (subject to caching) and on form submissions.
安装:
- Install and activate the plugin.
- In the Entra admin center, create an app registration (no redirect URI needed) and a client secret.
- In the Power Platform admin center, create an application user for that app registration in your environment and assign it a least-privilege security role: Read on the tables you publish, Create on the tables your forms write to. Do not use System Administrator.
- Enter tenant id, client id, client secret and environment URL under Settings, Dataverse Connect, or define them as
WBS_DATAVERSE_CONNECT_TENANT_ID,WBS_DATAVERSE_CONNECT_CLIENT_ID,WBS_DATAVERSE_CONNECT_CLIENT_SECRETandWBS_DATAVERSE_CONNECT_ENV_URLinwp-config.php(recommended). - Run "Test connection" on the settings page.
- Add a collection on the Collections tab and put
[wbsdvc_collection name="<key>"]on a page.
屏幕截图:
常见问题:
Do I need my own Dataverse environment?
Yes. The plugin is a front end for an environment you already own and administer; it ships with no data and no Microsoft account. Free developer environments are available from Microsoft at https://learn.microsoft.com/power-platform/developer/plan.
How is this different from Microsoft Power Pages?
Power Pages is Microsoft's hosted portal product with per-user and per-page-view licensing. This plugin serves the same Dataverse data from your own WordPress site on standard hosting, through the official Dataverse Web API. Dataverse remains the single source of truth; only the front end moves to WordPress.
Does WOODS Business Solutions see my data?
No. Your WordPress site talks directly to your own Microsoft endpoints (login.microsoftonline.com and your environment's *.dynamics.com URL). Nothing is sent to us, and the plugin contains no tracking or telemetry of any kind.
Where do my credentials live?
Preferably as constants in wp-config.php, which lock the matching settings fields and keep the secret out of the database entirely. Alternatively the settings page stores them in the WordPress options table; the secret is never displayed again after saving. Credentials are only ever used server-side and never reach the browser.
What data leaves my site?
Two things, both to your own Microsoft tenant: the configured credentials during token requests to login.microsoftonline.com, and the data of form submissions (the fields you mapped, typically name, email, phone and message) written to your Dataverse environment. Record data flows the other way, from your environment to your site. No other external requests are made.
Does it work with any table?
Any table the application user can read, standard or custom. A collection needs the table's logical name, its entity set name, a name column and the columns to display. Writes work against any table the application user may create records in, with values mapped to text columns; typed columns can be handled via a developer filter.
Are the templates customizable?
Yes. Copy any file from the plugin's templates/ directory into <your-theme>/wbs-connect-for-dataverse/ and edit the copy; the theme version wins, and child themes work too.
更新日志:
- Extension hooks for add-ons; per-connection token and cache keys.
- 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.
- 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, theme-overridable templates.