[Shopify] Add cues for Skipped Records and API Errors on Activities page

[Onat Buyukakkus (onbuyuka)]

What & why

Skipped records from background (Job Queue) Shopify syncs and logged API errors were invisible unless users manually opened the logs — the skipped-record notification relies on GuiAllowed, which is false in background sessions, and the Job Queue entry still shows Success. This adds two cues to the Shopify Activities page so users see issues at a glance:

• Skipped Records — count("Shpfy Skipped Record"), styled amber when > 0, drills down to the Shpfy Skipped Records page.
• API Errors — count("Shpfy Log Entry" where "Has Error" = true), styled red when > 0, drills down to the Shpfy Log Entries page filtered to errors.

New FlowFields (10, 11) on the Shpfy Cue table (30100) and two cue tiles on the Shpfy Activities page (30100). Both cues are unfiltered by date; the Retention Policy framework (1-month period on SystemCreatedAt, already registered for both tables) handles cleanup. Follows the existing cue pattern (Unmapped Customers, Unprocessed Orders, Synchronization Errors).

Linked work

Fixes AB#646260

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

• Built the Shopify Connector app locally (al_build) — packages with no new warnings.
• Manually validated on the Shopify Activities page: both cues render, color amber/red when counts are > 0, and drill down to the Skipped Records page and the error-filtered Log Entries page respectively.
• No automated tests added — the change is declarative cue metadata (FlowField CalcFormula plus page tiles and drill-downs) with no custom AL logic to unit-test; validated manually in BC.

Risk & compatibility

Low — additive only: two new FlowFields on an internal cue table plus two cue tiles. No table schema/data changes, no breaking changes. Read permissions already cover the underlying tables (Shpfy Skipped Record and Shpfy Log Entry are R in Shpfy - Read).

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Performance}$

The new "API Errors" FlowField counts "Shpfy Log Entry" rows filtered by "Has Error" = true, but the source table (Shpfy Log Entry, table 30115) only declares Key1 on "Entry No." with no key covering "Has Error" in SumIndexFields. Per CodeCop AA0232 / this article, a FlowField's source table needs a key that covers the CalcFormula's WHERE clause fields for the platform to answer CalcFields from SIFT; without it, every CalcFields call (triggered on each page activation via RefreshOnActivate = true and explicitly in the new OnAfterGetRecord trigger) falls back to a row-by-row scan of the log table, which grows unbounded over time.

Knowledge:

• microsoft/knowledge/performance/flowfield-source-key-needs-sumindexfields.md

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.31.4}

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Style}$

The new StyleExpr values are assigned from inline text literals ('Ambiguous', 'Favorable', 'Unfavorable') in OnAfterGetRecord(). These style tokens form a small contract with the page runtime, so leaving them as repeated magic strings makes typos and future drift harder to spot. Define named object-scope constants or locked labels for the allowed style values and assign those instead.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.31.4}

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Style}$

The page file ends without a trailing newline. Add a final newline after the closing brace so the file matches normal source-file formatting conventions and avoids repeated \ No newline at end of file diff noise in future changes.

Suggested fix (apply manually — could not be anchored as a one-click suggestion):

}

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.31.4}

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Testing}$

This change adds two new Shopify cue FlowFields plus page-side styling and drilldown behavior, but no Shopify test codeunit changes accompany it. Add tests that seed skipped-record and error-log data, open "Shpfy Activities", and verify the new cue counts, style states, and the "API Errors" drilldown filter so these UI/data behaviors are covered by regression tests.

Line mapping was unavailable, so this was posted as an issue comment.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.31.4}