"Warehouse Request" has wrong Table Relation for "Shipping Agent Service Code"
Maintainers usually reply within 1 day
@PredragMaricic is already working on this.
Since Oct 14, 2026.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- backend
Research direction
The wrong relation is on the "Shipping Agent Service Code" field at line 99 of src/Layers/W1/BaseApp/Warehouse/Request/WarehouseRequest.Table.al. Check the field's TableRelation against the Shipping Agent Services table and confirm that Validate fails on it. Done when the relation points to the Code field, optionally scoped by Shipping Agent Code, or the property is removed, and Validate succeeds. The issue names two alternatives, so check the single existing comment for which one the maintainers prefer.
Written by the indexing model from the issue text.
Description
Current Table Relation:
TableRelation = "Shipping Agent Services";
This prevents a Validate on the field.
Correct Table Relation:
TableRelation = "Shipping Agent Services".Code;
Or even:
TableRelation = "Shipping Agent Services".Code where("Shipping Agent Code" = field("Shipping Agent Code"));
In the base app this field is only ever assigned to. But if the wrong Table Relation is to be ignored, then it should be rather removed entirely.
- Dominant language
- AL
- Stars
- 697
- Forks
- 473
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 493
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
-
missing-info Team: Finance
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/BCApps#12893 · 5 comments ·
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 today. 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 2 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
-
[APAC][Extensibility Request][Report][28026][Financial Analysis Report] Move some variables to protected var for extensibilityPossibly taken @business-central-extensibility-bot claimed this 2 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
numberly/vault-db-injector#107 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
interledger/publisher-tools#931 ·
Maintainers usually reply within 1 day
-
area/import kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
refactor: replace numbered import aliases in platform/common, platform/fabricx, integration and ciOpencleanup go hacktoberfest priority: low skill: good first issue status: ready for dev
Difficulty 2/5 Half a day Newbie friendliness 72/100
hyperledger-labs/fabric-smart-client#2134 ·
Maintainers usually reply within 1 day
-
github-stale-ci-pr-closer: KV state is double-wrapped, never persists, and hits the depth-32 limitPossibly taken @VascoSch92 claimed this today. Openpriority:medium ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenHands/extensions#781 ·
Maintainers usually reply within 1 day