636017 Move CRM report action tooltips to report objects

[V-CWurtzen]

What & why

Moves the report action ToolTips for the CRM / Marketing 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.

Reports covered (16): Campaign - Details, Contact - Labels, Create Conts. from Bank Accs., Create Conts. from Customers, Create Conts. from Vendors, Delete Campaign Entries, Delete Interaction Log Entries, Delete Logged Segments, Delete Opportunities, Delete Tasks, Questionnaire - Handouts, Relocate Attachments, Sales Cycle - Analysis, Salesperson - Opportunities, Salesperson - Tasks, Team - Tasks. All source tooltips are descriptive (no stubs).

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 16 reports; duplicate removed from the W1 actions that run them (Marketing/segment/contact pages and role centers, plus the Administrator role center and Data Administration). 29 files.
• Country layers (commit 2): the W1 move is propagated to the forked country layers as required by the Miapp sync gate (VerifyMiappSync):
  • 10 page forks across APAC, BE, CH, DACH, NA, NL, NO, RU: duplicate ToolTip removed from the covered actions (33 lines).
  • 2 report forks (APAC ContactLabels, RU CreateContsfromVendors): report-level ToolTip added to match W1.

Total: 41 files (29 W1 + 12 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 100% tooltip lines (report ToolTip additions + page-action ToolTip removals), with BOM/EOL preserved and no other lines changed. 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 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) and Bank (#9540) on the new BCApps pipeline.

[github-actions]

Copilot PR Review

Iteration 1 · Outcome: completed

All sub-skills completed; the diff relocates ToolTip properties from page actions onto the Report objects they run, a mechanical, low-risk refactor with no logic changes. No sub-skill found applicable knowledge violated, and the self-review pass found no cross-cutting defects.

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

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.}