microsoft / microsoft/ALAppExtensions

Extensibility request — additional bank payment types in general journal posting (check ledger entry creation)

Open
#30,435 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

missing-info
Dominant language
AL
Stars
988
Forks
692
Avg merge
49m
Merged PRs (30d)
1

Description

Why do you need this change?

We are an end customer on Dynamics NAV 2015 preparing a migration to Business Central on-premises. Our NAV customization extends general journal posting so that an additional bank payment type ("Credit Card") creates check ledger entries in the same manner as the standard Manual Check handling (codeunit 12, Gen. Jnl.-Post Line area). We request extensibility (published events or an extensible enum with accompanying event coverage) sufficient for an extension to add a bank payment type and create the corresponding check ledger entries during posting, without modifying the base application. If current versions already expose sufficient integration events for this scenario, a pointer to them would fully resolve this request.

Describe the request

We are an end customer on Dynamics NAV 2015 preparing a migration to Business Central on-premises. Our NAV customization extends general journal posting so that an additional bank payment type ("Credit Card") creates check ledger entries in the same manner as the standard Manual Check handling (codeunit 12, Gen. Jnl.-Post Line area). We request extensibility (published events or an extensible enum with accompanying event coverage) sufficient for an extension to add a bank payment type and create the corresponding check ledger entries during posting, without modifying the base application. If current versions already expose sufficient integration events for this scenario, a pointer to them would fully resolve this request.

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 by reviewing codeunit 12, Gen. Jnl.-Post Line, and the standard Manual Check handling described in the issue. Trace whether existing integration events cover bank payment types and check ledger entry creation. Done means documenting sufficient extension points, or defining the event and enum coverage needed for Credit Card posting without modifying the base application.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.