[FI][Report][393][Suggest Vendor Payments] Add event/function OnAfterIncludeVendor(Vendor, VendorBalance, Result) as per W1 version
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- payments
Research direction
The change belongs to report 393, Suggest Vendor Payments, in the Finland localization. Compare it with the W1 version of the same report to find where OnAfterIncludeVendor is raised, since the request is to match that signature (Vendor, VendorBalance, Result). Done means the FI report raises the same event with the same parameters, and the FI build still compiles. Check with the maintainers first, because the reporter has not been assigned and the request is an extensibility change.
Written by the indexing model from the issue text.
Description
Why do you need this change?
We've an extension based on W1 that is deployed in several countries.
We use an event from [Report][393][Suggest Vendor Payments] that is missing in the Finland (FI) version.
Event is available in (at least) in W1, GB, PL, SE, NO, LV, DK, IS. versions 28.3, 28.4, 28.5, 29.
Describe the request
Please add to [Report][393][Suggest Vendor Payments] in the FI Version the W1 event/function OnAfterIncludeVendor(Vendor, VendorBalance, Result).
Checked against FI version 29 and it is still missing the w1 event.
´
Object: [Report][393][Suggest Vendor Payments]
event/function: OnAfterIncludeVendor(Vendor, VendorBalance, Result)
notes: Event is available in (at least) in W1, GB, PL, SE, NO, LV, DK, IS. versions 28.3, 28.4, 28.5, 29.
Provide an implementation (optional)
- I will provide the implementation for this extensibility request
- Dominant language
- AL
- Stars
- 697
- Forks
- 473
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 503
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/BCApps
-
missing-info Team: Finance
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/BCApps#12900 · 1 comment ·
Maintainers usually reply within 1 day
-
[W1][Extensibility Request][Subscription Billing] Remove local access from InitTempTable() procedure on page 8025 "Contract Price Update"Possibly taken @business-central-extensibility-bot claimed this 2 days ago. OpenApproved ext-ready-to-implement request-for-external Team: Finance
Difficulty 1/5 Under an hour Newbie friendliness 70/100
microsoft/BCApps#12775 · 2 comments ·
Maintainers usually reply within 1 day
-
[W1][MultiObjects] Output journal lines: event after CheckWhse in codeunits 5406 "Output Jnl.-Expl. Route" and 5510 "Production Journal Mgt"Possibly taken @PredragMaricic claimed this 3 days ago. OpenApproved Team: SCM
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
microsoft/BCApps#12652 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
"Warehouse Request" has wrong Table Relation for "Shipping Agent Service Code"Possibly taken @PredragMaricic claimed this 3 days ago. OpenApproved Team: SCM
Difficulty 1/5 Under an hour Newbie friendliness 75/100
microsoft/BCApps#12623 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
[APAC][Extensibility Request][Report][28026][Financial Analysis Report] Move some variables to protected var for extensibilityPossibly taken @business-central-extensibility-bot claimed this 4 days ago. OpenApproved ext-ready-to-implement request-for-external Team: Finance
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/BCApps#12586 · 1 comment ·
Maintainers usually reply within 1 day
All issues in microsoft/BCApps
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
polarsource/polar#15580 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
StabilityNexus/Chainvoice#294 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jazzband/django-payments#502 ·
-
bug complexity: trivial frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
milepost-labs/milepost#452 ·
Maintainers usually reply within 1 day