microsoft / microsoft/BCApps

Connectivity Apps: replace Continia Payment Management registrations with Continia Banking

Open
#11,317 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Team: Finance
Dominant language
AL
Stars
683
Forks
459
Avg merge
3d 26m
Merged PRs (30d)
633

Description

Describe the issue

The banking connectivity apps list (Connectivity App Definitions, src/Apps/W1/ConnectivityApps) promotes Continia Payment Management for NL, DK and NO. Continia has replaced Payment Management with Continia Banking as its bank-integration product for Business Central, so the curated list now points customers at a superseded product in those three markets — and offers no Continia option at all in the six further markets where Continia Banking is published on AppSource (AT, CH, DE, FI, GB, SE).

Two concrete defects in the registrations as they stand today:

  1. The provider support URL is dead. All three Payment Management entries use https://www.continia.com/inspiration/solution-usage/connect-your-banks-to-business-central/, which now returns HTTP 404. A customer clicking through from the banking apps list reaches an error page.
  2. The AppSource links promote a retired product. The offers behind the three entries are the Payment Management listings, not the product Continia is now shipping and supporting.

Continia is already a participant in the Connectivity Apps program — Payment Management is registered in this list today — so this is an update to an existing participant's registrations rather than a new onboarding.

Expected behavior

The banking connectivity apps list should offer Continia Banking in every localization where Continia publishes it on AppSource, with working AppSource and support URLs, and should no longer promote Continia Payment Management:

Localization AppSource product App id
AT Continia Banking (AT) 5028cc6e-2288-4894-84a0-5934504a660c
CH Continia Banking (CH) 99f643c2-bf89-4fe2-bb3a-e2a380635faf
DE Continia Banking (DE) 009dc3e3-3080-4e48-92fc-1bc7a0ef4caa
DK Continia Banking (DK) 62235b56-656d-4e85-989b-fd47130bf4e5
FI Continia Banking (FI) fb89b25e-b8be-4d31-b509-a29de965f12b
GB Continia Banking (UK) 4b595a5f-4e4f-49fb-9d25-b052a309f9c5
NL Continia Banking (NL) f2303be5-5ecd-44db-b4e8-b1be22af4a53
NO Continia Banking (NO) e7b8a6d4-3c4e-4f8b-9a6e-8d3b8a6d4f8b
SE Continia Banking (SE) ffec28be-01ad-4e63-bcee-bed076b3aecc

All three markets Payment Management covered today (NL, DK, NO) keep Continia representation, and six markets gain it.

Steps to reproduce
  1. Open a Business Central environment using the DK localization (NL or NO reproduce the same way).
  2. Open a Bank Account Card and choose the Connect to Banks action, or open the Banking Apps page directly.
  3. Observe the entry Continia Payment Management (DK) in the list.
  4. Open that entry and follow the provider support link — the page returns HTTP 404.
  5. Repeat steps 1–2 in an AT, CH, DE, FI, GB or SE company: no Continia entry is offered, even though Continia Banking (<CC>) is published on AppSource for each of those localizations (see the table above).
Additional context
  • This contribution has been discussed with Søren Alexandersen (Microsoft), who is expecting the PR.
  • The implementation is already open as PR #10640, which the automated reviewer has assessed as Accept / Risk: Low / no suggestions. It is waiting only on an approved issue to link to.
  • Every AppSource URL the change generates has been verified against the live marketplace: the rendered product name on each of the nine listings matches the name the code derives.
  • One detail worth flagging for reviewers: AppSource lists the GB localization as Continia Banking (UK) under offer id continia-banking-uk, so the product code is passed separately from the BC localization code. Deriving it from GB would produce a dead link.
  • The change is confined to connectivity app registration metadata inside an Access = Internal codeunit — no schema, posting, upgrade or persisted-data impact. It affects the discovery/promotion surface only.

Note: this is filed with the bug template because the repository offers no template for connectivity app registration changes and blank issues are disabled. The dead support URL and the retired product links are genuine defects in the current data, but the substance of the request is a registration update — please retitle or relabel as appropriate.

I will provide a fix for a bug
  • I will provide a fix for a bug

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in src/Apps/W1/ConnectivityApps and inspect the Access = Internal connectivity app registration codeunit. Compare the existing Continia entries with the nine localization, product, and AppSource identifiers listed in the issue, paying special attention to the GB product code. Done means the list contains Continia Banking for all nine markets, uses working support and AppSource URLs, and no longer promotes Payment Management.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.