Table 1615 "Office Job Journal"
Base Application · Microsoft.CRM.Outlook
Across versions
- BC23present
- BC245 fields changed
- BC25-27unchanged
- BC284 fields changed
- BC29-30unchanged
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.CRM.Outlook · captioned “Office Project Journal” · BC23-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 1615 “Office Job Journal” (1 Learn page).
Properties
| Property | Value |
|---|---|
| Caption | Office Project Journal |
| 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 Δ BC28 | Code[20] | Specifies the number of the related project. | |
| 2 | Job Task No. Δ BC24 Δ BC28 | Code[20] | Specifies the number of the related project task. | |
| 3 | Job Planning Line No. Δ BC24 | Integer | Project Planning Line No. caption | |
| 4 | Job Journal Template Name Δ BC24 Δ BC28 | Code[10] | Specifies the journal template that is used for the project journal. | TableRelation Table 209 “Job Journal Template” (“Job Journal Template”.Name where(“Page ID” = const(201), Recurring = const(false))) |
| 5 | Job Journal Batch Name Δ BC24 Δ BC28 | Code[10] | Specifies the journal batch that is used for the project journal. | TableRelation Table 237 “Job Journal Batch” (“Job Journal Batch”.Name where(“Journal Template Name” = field(“Job Journal Template Name”))) |
Keys
- Key1: Job No., Job Task No., Job Planning Line No. (clustered)
Procedures
Initialize(JobPlanningLine: Record "Job Planning Line")
Relations
- Job Journal Template Name: TableRelation Table 209 “Job Journal Template”
- Job Journal Batch Name: TableRelation Table 237 “Job Journal Batch”
Pages and codeunits on this table
- Page 1615 “Office Job Journal” (source table)
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: "Office Job Journal"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.