tableProjectsofficial - Microsoftderived - from the source, no model text

Table 1034 "Job Planning Line - Calendar"

Base Application · Microsoft.Projects.Project.Planning

Across versions

  1. BC23present
  2. BC242 fields changed
  3. BC25-27unchanged
  4. BC281 fields changed
  5. BC29-30unchanged

Neighbourhood 1 connected objects and pages

Table 1003 "Job Planning Line" (relates to, 3 links)Job Planning Line

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Projects.Project.Planning · captioned “Project Planning Line - Calendar” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Project Planning Line - Calendar
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 1003 “Job Planning Line” (“Job Planning Line”.“Job No.”)
2 Job Task No. Δ BC24 Code[20] Project Task No. caption TableRelation Table 1003 “Job Planning Line” (“Job Planning Line”.“Job Task No.”)
3 Planning Line No. Integer — TableRelation Table 1003 “Job Planning Line” (“Job Planning Line”.“Line No.”)
4 Resource No. Code[20] — TableRelation Resource.“No.”
6 Planning Date Date —
7 Quantity Δ BC28 Decimal —
8 Description Text[100] —
9 UID Guid —
10 Sequence Integer —

Keys

  • Key1: Job No., Job Task No., Planning Line No. (clustered)

Procedures

  • HasBeenSent(JobPlanningLine: Record "Job Planning Line"): Boolean
  • InsertOrUpdate(JobPlanningLine: Record "Job Planning Line")
  • ShouldSendCancellation(JobPlanningLine: Record "Job Planning Line"): Boolean
  • ShouldSendRequest(JobPlanningLine: Record "Job Planning Line"): Boolean

Triggers

OnInsert, OnModify

Relations

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 Planning Line - Calendar"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources