What this category of data looks like
Daily revenue report data for property management scenarios comes from the property fee management system, public area operation ledger, and energy consumption and maintenance operation system. It updates daily at midnight, syncing calculated data from the previous day. Each record corresponds to the revenue breakdown of a single property project on one day. Fields include: project unique identifier, statistical date, actual property fee revenue, public area operation income, maintenance and energy consumption costs, and net revenue amount. All monetary fields use Chinese Yuan as their unit. The data focuses on operating revenue for a single project on one day, and does not include cross-project or multi-cycle aggregate statistics.
What constraints these characteristics impose on the sharing and embedding workflow
The single-project single-day data structure requires the sharing and embedding process to support dynamic filtering by project identifier and statistical date. Without this, it cannot accurately display the specified property's daily revenue. The daily update schedule requires shared link cache durations to match the data update cycle, to avoid displaying outdated information. The monetary field attributes require embedded display formats to adapt to financial reading habits, and cannot arbitrarily truncate or change units. The unique association between data and property projects requires sharing authentication to bind project permission scopes, preventing unauthorized access to operating data across projects. Daily report data has strong timeliness, so embedded interface loading wait times must be controlled within a reasonable range to avoid impacting user experience.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
share_auth_required | true | Property management operating data involves project privacy, so authentication must be enabled to restrict access scope |
share_expire_hours | 24 hours | Matches the daily update schedule of daily report data, avoids displaying outdated information |
allow_dynamic_params | ["project_id", "stat_date"] | Supports filtering data by property project and statistical date, matches the single-project single-day data structure |
iframe_sandbox | "allow-scripts allow-same-origin allow-popups" | Adapts to script rendering and cross-domain interaction requirements for embedding scenarios, supports jump trigger logic |
api_response_timeout | 5000 milliseconds | Adapts to the small size of daily report data, shortens loading wait times |
render_reference_link | true | Supports rendering reference links returned by third-party APIs, meets scenario display requirements |
The parameter values provided on this page are common recommended starting points for defining configurations. Actual values are affected by material form, data volume, and business rules. Specific issues require individual analysis. It is recommended to test on your own samples before finalizing settings.
Three common configuration errors
- Symptom: The embedded page returns a 403 status code, with a prompt indicating no access permission. Cause: The
share_auth_requiredconfiguration is not enabled, or the shared link is not bound to the permission scope of the specified property project. - Symptom: AI reply content cannot trigger local application jumps. Cause: The
allow-popupspermission in theiframe_sandboxconfiguration is not set, or the identification field required for the jump is not added to the dynamic parameters. - Symptom: Reference links in the shared page are not rendered as clickable formats. Cause: The
render_reference_linkconfiguration is not enabled, or the reference data field is not correctly passed in the API request.
How to confirm the configuration is correctly set
- Call the shared link generation interface, pass test project identifier and statistical date parameters, verify that the returned link includes the corresponding dynamic parameters.
- Embed the generated shared link in a local test environment, verify that data loads normally and no permission-related errors are displayed.
- After triggering a third-party API request, verify that the embedded page correctly renders reference data as clickable formats.
- After triggering the data synchronization process, verify that the content of the shared link updates to the latest data according to the configured cache strategy.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.