microsoft / microsoft/BCApps

[Bug]: Work Description is not transferred from Sales Order to Prepayment Invoice in BC28 when "Calc. Inv. Discount" setting is toggled ON in Sales & Receivables Setup (use to work in BC27)

Open
#8,774 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Describe the issue

[Bug]: Work Description is not transferred from Sales Order to Prepayment Invoice in BC28 when "Calc. Inv. Discount" setting is toggled ON in Sales & Receivables Setup (use to work in BC27)

Expected behavior

Work Description is supposed to be transferred from Sales Order to Prepayment Invoice

Steps to reproduce
  1. In Sales & Receivables Setup: Toggle setting "Calc. Inv. Discount" ON (NOTE! THIS IS KEY!)
  2. Create Sales Order
  3. Enter Customer No.
  4. Enter Work Description
  5. Enter Item No.
  6. Enter Quantity
  7. Enter Prepayment % (you may have to add this field with Personalize)
  8. Post Prepayment Invoice (Actions -> Posting -> Prepayment -> Post Prepayment Invoice...)
  9. Look at the Posted Prepayment Invoice (Related -> Prepayment -> Prepayment Invoices)
  10. The Posted Prepayment Invoice has no Work Description
Additional context
Image

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 reproducing the issue with "Calc. Inv. Discount" enabled in Sales & Receivables Setup, following the listed Sales Order and Prepayment Invoice steps. Trace the prepayment posting flow from the Sales Order to the Posted Prepayment Invoice and verify that Work Description is transferred; add regression coverage if the repository's existing tests identify a suitable location.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.