Skip to content

636017 Move Fixed Assets report action tooltips to report objects#9546

Open
V-CWurtzen wants to merge 2 commits into
mainfrom
features/636017-FixedAssets-move-page-action-tooltips-to-report
Open

636017 Move Fixed Assets report action tooltips to report objects#9546
V-CWurtzen wants to merge 2 commits into
mainfrom
features/636017-FixedAssets-move-page-action-tooltips-to-report

Conversation

@V-CWurtzen

@V-CWurtzen V-CWurtzen commented Jul 16, 2026

Copy link
Copy Markdown

What & why

Moves the report action ToolTips for the Fixed Assets reports off the page actions that run them and onto the report objects themselves, and integrates that move into every forked country layer. The tooltip is now defined once on the report and applies wherever the report is invoked, and the now-duplicate ToolTip is removed from the page actions in W1 and its country forks.

29 reports covered — the Fixed Asset - Book Value 01/02, Fixed Asset - List/Register/Acquisition List/G-L Analysis reports, the Insurance - Analysis/List/Coverage Details/Tot. Value Insured/Uninsured FAs/Register set, Calculate Depreciation, Copy Depreciation Book, Create FA Depreciation Books, Cancel FA Ledger Entries, Copy FA Entries to G/L Budget, the Date Compress FA/Insurance/Maint. Ledger set, the Delete Empty FA/Insurance Registers set, and others.

Where only a Run the X report. stub existed (FA Posting Group - Net Change, Index Fixed Assets, Index Insurance, Maintenance - Analysis/Details/Next Service, Maintenance Register), it is hoisted as the sole option — happy to replace with better wording if a reviewer suggests it. Reports with ObsoleteState = Pending/Removed are skipped (3).

This is part of the "move report action tooltips to report objects" cleanup (CP0529-331 / slice 636017).

Changes

  • W1 (commit 1): report-level ToolTip added to the 29 reports; duplicate removed from the W1 actions that run them (Fixed Asset card/list and FA/Insurance/Maintenance pages and role centers, plus the Accountant/Administrator role centers and Data Administration). 41 files.
  • Country layers (commit 2): the W1 move is propagated to the forked country layers as required by the Miapp sync gate (VerifyMiappSync):
    • 59 page forks across 19 country layers: duplicate ToolTip removed from the covered actions (462 lines).
    • 10 report forks (FR: CalculateDepreciation, CopyDepreciationBook, CancelFALedgerEntries, CopyFAEntriestoGLBudget, IndexFixedAssets, FixedAssetBookValue01/02; GB CopyDepreciationBook; IT/RU CalculateDepreciation): report-level ToolTip added to match W1.
    • 1 no-op integration (NA AccountantRoleCenter): the sync gate requires every fork of a changed W1 file in the changelist; it carries no covered action, so there is nothing to remove.

Total: 111 files (41 W1 + 70 country), tooltip-only.

Linked work

Fixes AB#636017

How I validated this

  • I read the full diff and it contains only changes I intended.
  • I built the affected app(s) locally with no new analyzer warnings.
  • I ran the change in Business Central and confirmed it behaves as expected.
  • I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome

Metadata-only change (ToolTip property). The diff is tooltip-only (report ToolTip additions + page-action ToolTip removals), with BOM/EOL preserved and no other lines changed; the only non-tooltip edit is a single trailing newline on NA AccountantRoleCenter.Page.al (no-op sync touch). Country propagation was produced by running Invoke-Miapp to identify the fork set, then applying the move surgically (Invoke-Miapp's auto-merge mis-aligned on the structurally-divergent role centers, so its output was not used directly). The set of changed forks matches exactly what VerifyMiappSync requires — no missing forks, no extras.

No tests added: ToolTip is a design-time metadata property with no runtime behavior to assert; there is no existing tooltip test harness for these objects.

Risk & compatibility

Low. No code, schema, table, or behavior change — only the ToolTip design property moves from page action to report, in W1 and its country forks. No upgrade/data impact, no permission/telemetry impact, no breaking change. Same cleanup pattern already merged for Warehouse, Manufacturing, Service, Sales and Inventory, landed as the Pricing pilot (#9433), and applied to CashFlow (#9528), Finance (#9526), Bank (#9540), CRM (#9544) and Cost Accounting (#9545) on the new BCApps pipeline.

Move the report action ToolTips for 29 Fixed Assets reports onto the report
objects and remove the now-duplicate ToolTip from the W1 page actions that
run them (Fixed Asset card/list and FA/Insurance/Maintenance pages and role
centers, plus the Accountant/Administrator role centers and Data
Administration).

Covers the Fixed Asset - Book Value/List/Register/G-L Analysis/Acquisition
reports, the Insurance - Analysis/List/Coverage/Register set, Calculate
Depreciation, Copy Depreciation Book, the Date Compress FA/Insurance/Maint.
Ledger set, the Delete Empty FA/Insurance Registers set, and others. Where
only a "Run the X report." stub existed (FA Posting Group - Net Change,
Index Fixed Assets, Index Insurance, the Maintenance - Analysis/Details/
Next Service/Register set) it is hoisted as the sole option. Reports with
ObsoleteState = Pending/Removed are skipped (3).
Integrate the W1 Fixed Assets tooltip move into the forked country layers,
as required by the Miapp sync gate (VerifyMiappSync):
- 59 page forks across 19 country layers: removed the duplicate ToolTip
  from the covered-report actions (462 lines).
- 10 report forks (FR: CalculateDepreciation, CopyDepreciationBook,
  CancelFALedgerEntries, CopyFAEntriestoGLBudget, IndexFixedAssets,
  FixedAssetBookValue01/02; GB CopyDepreciationBook; IT/RU
  CalculateDepreciation): added the W1 report-level ToolTip.
- 1 no-op integration (NA AccountantRoleCenter): the sync gate requires
  every fork of a changed W1 file in the changelist; it carries no covered
  action, so there is nothing to remove.
@V-CWurtzen V-CWurtzen requested a review from a team July 16, 2026 16:45
@github-actions github-actions Bot added this to the Version 29.0 milestone Jul 16, 2026
{
ApplicationArea = FixedAssets;
Caption = 'Index Fixed Assets';
ToolTip = 'Run the Index Fixed Assets report.';

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

$\textbf{🟡\ Medium\ Severity\ —\ Style} \quad \color{gray}{\texttt{\small Iteration\ 1}}$

Several of the newly-added Report ToolTips only restate the object's caption/name ("Run the X report.") instead of describing what the report shows or does, so they add no information beyond the caption already visible on the action/Tell Me entry.

This diverges from the surrounding tooltips in the same PR (e.g. 'Calculate Depreciation', 'Fixed Asset - Book Value 01') which describe purpose and content, and from the field-tooltip convention in BCQuality (microsoft/knowledge/style/tooltip-required-on-page-fields.md) that tooltips should describe what the item shows/does rather than just naming it. Affected locations: src/Layers/W1/BaseApp/FixedAssets/FixedAsset/IndexFixedAssets.Report.al:18 ('Run the Index Fixed Assets report.'), src/Layers/FR/BaseApp/FixedAssets/FixedAsset/IndexFixedAssets.Report.al:18 (same text), src/Layers/W1/BaseApp/FixedAssets/Insurance/IndexInsurance.Report.al:16 ('Run the Index Insurance report.'), src/Layers/W1/BaseApp/FixedAssets/Maintenance/MaintenanceAnalysis.Report.al:15 ('Run the Maintenance Analysis report.'), src/Layers/W1/BaseApp/FixedAssets/Maintenance/MaintenanceDetails.Report.al:15 ('Run the Maintenance Details report.'), src/Layers/W1/BaseApp/FixedAssets/Maintenance/MaintenanceNextService.Report.al:13 ('Run the Maintenance Next Service report.'), src/Layers/W1/BaseApp/FixedAssets/Maintenance/MaintenanceRegister.Report.al:14 ('Run the Maintenance Register report.'), and src/Layers/W1/BaseApp/FixedAssets/Reports/FAPostingGroupNetChange.Report.al:19 ('Run the FA Posting Group - Net Change report.'). Recommend rewriting each to describe the report's actual content/purpose, consistent with the other ToolTips added in this PR.

Agent judgement — not directly backed by a BCQuality knowledge article.

👍 useful · ❤️ especially valuable · 👎 wrong - reply with why

{
ApplicationArea = FixedAssets;
Caption = 'Fixed Asset List';
ToolTip = 'View the list of fixed assets that exist in the system .';

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

$\textbf{🟡\ Medium\ Severity\ —\ Style} \quad \color{gray}{\texttt{\small Iteration\ 1}}$

New Report ToolTip has a stray space before the terminating period: "View the list of fixed assets that exist in the system ." should read "...in the system." (no space before the period).

This is user-facing text shown as a hover tooltip and in Tell Me search results.

Agent judgement — not directly backed by a BCQuality knowledge article.

👍 useful · ❤️ especially valuable · 👎 wrong - reply with why

@github-actions

Copy link
Copy Markdown
Contributor

Copilot PR Review

Iteration 1 · Outcome: completed

PR is a pure metadata/UI-text refactor moving ToolTip text from role-center/list-page actions to the Report objects they run (Fixed Assets area, all country layers). No business logic changed. Style-domain review found two AL-quality issues in the newly-added report ToolTips; all other leaves found nothing applicable to this diff.

Knowledge source: https://github.com/microsoft/BCQuality@186d8a131465475c79244d994acb872cd5c0d4bf

Findings by domain

Findings split into Knowledge-backed (cite a BCQuality article) and Agent (the agent's own judgement, no matching BCQuality rule).

Domain Findings Knowledge-backed Agent Inline Fallback
Style 2 0 2 2 0

Totals: 0 knowledge-backed · 2 agent findings.

Orchestrator pre-filter (2 file(s) excluded)

  • layer-disabled (knowledge) : 2 file(s)

Findings produced by the AL review agent v1.7.3. Reply 👎 on any inline comment to flag false positives.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant