Table 1020 "Job Usage Link"
Base Application · Microsoft.Projects.Project.Job
Across versions
- BC23present
- BC242 fields changed, 1 fields added
- BC25-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Projects.Project.Job · captioned “Project Usage Link” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Project Usage Link |
| DataClassification | CustomerContent |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Job No. Δ BC24 | Code[20] | Project No. caption | TableRelation Table 167 “Job” |
| 2 | Job Task No. Δ BC24 | Code[20] | Project Task No. caption | TableRelation Table 1001 “Job Task” (“Job Task”.“Job Task No.” where(“Job No.” = field(“Job No.”))) |
| 3 | Line No. | Integer | — | TableRelation Table 1003 “Job Planning Line” (“Job Planning Line”.“Line No.” where(“Job No.” = field(“Job No.”), “Job Task No.” = field(“Job Task No.”))) |
| 4 | Entry No. | Integer | — | |
| 5 | External Id + BC24 | Guid | — | DataClassification SystemMetadata |
Keys
- Key1: Job No., Job Task No., Line No., Entry No. (clustered)
- Key2: External Id
Procedures
Create(JobPlanningLine: Record "Job Planning Line"; JobLedgerEntry: Record "Job Ledger Entry")
Relations
- Job Task No.: TableRelation Table 1001 “Job Task”
- Line No.: TableRelation Table 1003 “Job Planning Line”
- Job No.: TableRelation Table 167 “Job”
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "Job Usage Link"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.