microsoft / microsoft/ALAppExtensions
[Extensibility Bug] Missing "Ship-to Name" on "Posted Sales Invoices" in ES
Nobody has claimed this yet.
- Dominant language
- AL
- Stars
- 988
- Forks
- 692
- Avg merge
- 49m
- Merged PRs (30d)
- 1
Description
Why do you need this change?
Our App could be Build and Published on W1 but not on ES since we have an reference on the control.
Describe the request
I think this is small conversion bug.
Just Change it, or set the old control to obsolete and introduce it like in w1.
Field in W1:
field("Ship-to Name"; Rec."Ship-to Name")
https://github.com/StefanMaron/MSDyn365BC.Code.History/blob/w1-26/BaseApp/Source/Base%20Application/Sales/History/PostedSalesInvoices.Page.al#L152
Field in ES:
field("<Ship-to Code>"; Rec."Ship-to Name")
https://github.com/StefanMaron/MSDyn365BC.Code.History/blob/es-26/BaseApp/Source/Base%20Application/Sales/History/PostedSalesInvoices.Page.al#L152
Internal work item: AB#598451
Contributor 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.
Research direction
Compare BaseApp/Source/Base Application/Sales/History/PostedSalesInvoices.Page.al at the referenced line in the w1-26 and es-26 histories. Verify the ES Posted Sales Invoices page uses the intended Ship-to Name field and confirm the app can build and publish for ES.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100