bc-source
Look up Business Central base application source code (tables, pages, codeunits, events) from MSDyn365BC.Sandbox.Code.History. Use this to verify object structures, find event publishers, or check field definitions.
What this skill does
# /bc-source — BC Base App Source Lookup
Reference repository for BC base application AL source code across all versions.
Use this when you need to verify table structures, find event publishers, check page layouts,
or understand how standard BC objects work.
## Setup (one-time per session)
Clone the correct branch for the customer's BC version. Check `app.json` for the runtime version.
```bash
# Clone to /tmp/bc-source (shallow, fast)
git clone -b w1-27 --single-branch --depth 1 \
https://github.com/StefanMaron/MSDyn365BC.Sandbox.Code.History.git \
/tmp/bc-source 2>/dev/null || echo "Already cloned"
```
For country-specific localizations, use the country code:
```bash
git clone -b us-27 --single-branch --depth 1 ...
```
Branch naming: `{country}-{major}` where country is `w1` (worldwide), `us`, `de`, `fr`, etc.
## Finding objects
The base app source is in `BaseApp/Source/Base Application/`.
### Find a table by name or ID
```bash
grep -rl "table [0-9]* \"Purchase Header\"" /tmp/bc-source/BaseApp/Source/ | head -5
# or by ID
grep -rl "table 38 " /tmp/bc-source/BaseApp/Source/ | head -5
```
### Find a page
```bash
grep -rl "page [0-9]* \"Purchase Order\"" /tmp/bc-source/BaseApp/Source/ | head -5
```
### Find a codeunit
```bash
grep -rl "codeunit [0-9]* \"Approvals Mgmt.\"" /tmp/bc-source/BaseApp/Source/ | head -5
```
### Find event publishers
```bash
# Find all integration events in a specific codeunit
grep -n "IntegrationEvent" /tmp/bc-source/BaseApp/Source/**/ApprovalsMgmt.Codeunit.al
```
### Find all fields on a table
```bash
# Read the table file to see all fields
cat /tmp/bc-source/BaseApp/Source/**/PurchaseHeader.Table.al | head -200
```
### Search for any pattern across base app
```bash
grep -rn "OnAfterCheck.*ApprovalPossible" /tmp/bc-source/BaseApp/Source/
```
## Common use cases
1. **Verify a field exists on a table** before writing a table extension
2. **Find the right event** to subscribe to (search for `IntegrationEvent` in relevant codeunits)
3. **Check field types and properties** (DataClassification, OptionMembers, etc.)
4. **Understand data flow** by reading codeunit procedures
5. **Find page controls** to determine where to add extension fields
## Structure reference
```
/tmp/bc-source/
├── BaseApp/Source/Base Application/ ← Main app (tables, pages, codeunits)
├── System Application/Source/ ← System utilities
├── BusinessFoundation/Source/ ← Foundation types
└── ...other modules
```
Within BaseApp, files follow the pattern:
- `{ObjectName}.Table.al`
- `{ObjectName}.Page.al`
- `{ObjectName}.Codeunit.al`
- `{ObjectName}.Report.al`
- `{ObjectName}.Enum.al`
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.