Page 1001 "Job Task Lines Subform"
Base Application · Microsoft.Projects.Project.Job
Across versions
- BC23present
- BC242 procedures added
- BC25-26unchanged
- BC271 procedures removed
- BC28-30unchanged
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Projects.Project.Job · captioned “Project Task Lines Subform” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Project Task Lines Subform |
| SourceTable | Job Task |
| PageType | ListPart |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Control1 | Job No. | Job No. | Specifies the number of the related project. from the table field |
| Job Task No. | Job Task No. | Specifies the number of the related project task. from the table field | |
| Description | Description | Specifies a description of the project task. You can enter anything that is meaningful in describing the task. The description is copied and used in descriptions on the project planning line. from the table field | |
| Job Task Type | Job Task Type | Specifies the purpose of the account. Newly created accounts are automatically assigned the Posting account type, but you can change this. Choose the field to select one of the following five options: from the table field | |
| Totaling | Totaling | Specifies an interval or a list of project task numbers. from the table field | |
| Customer No. | Sell-to Customer No. | Specifies the number of the customer who will receive the products and be billed by default for the project task. from the table field | |
| Bill-to Customer No. | Bill-to Customer No. | Specifies the number of the customer who pays for the project task. | |
| Job Posting Group | Job Posting Group | Specifies the project posting group of the task. from the table field | |
| Location Code | Location Code | Specifies the location code of the task. from the table field | |
| Bin Code | Bin Code | Specifies a bin code for specific location of the task. from the table field | |
| WIP-Total | WIP-Total | Specifies the project tasks you want to group together when calculating Work In Process (WIP) and Recognition. from the table field | |
| WIP Method | WIP Method | Specifies the name of the Work in Process calculation method that is associated with a project. The value in this field comes from the WIP method specified on the project card. from the table field | |
| Start Date | Start Date | Specifies the start date for the project task. The date is based on the date on the related project planning line. from the table field | |
| End Date | End Date | Specifies the end date for the project task. The date is based on the date on the related project planning line. from the table field | |
| Budget (Total Cost) | Schedule (Total Cost) | Specifies, in the local currency, the total budgeted cost for the project task during the time period in the Planning Date Filter field. | |
| Budget (Total Price) | Schedule (Total Price) | Specifies, in local currency, the total budgeted price for the project task during the time period in the Planning Date Filter field. | |
| Usage (Total Cost) | Usage (Total Cost) | Specifies, in local currency, the total cost of the usage of items, resources and general ledger expenses posted on the project task during the time period in the Posting Date Filter field. | |
| Usage (Total Price) | Usage (Total Price) | Specifies, in the local currency, the total price of the usage of items, resources and general ledger expenses posted on the project task during the time period in the Posting Date Filter field. | |
| Contract (Total Cost) | Contract (Total Cost) | Specifies, in local currency, the total billable cost for the project task during the time period in the Planning Date Filter field. | |
| Contract (Total Price) | Contract (Total Price) | Specifies, in the local currency, the total billable price for the project task during the time period in the Planning Date Filter field. | |
| Contract (Invoiced Cost) | Contract (Invoiced Cost) | Specifies, in the local currency, the total billable cost for the project task that has been invoiced during the time period in the Posting Date Filter field. | |
| Contract (Invoiced Price) | Contract (Invoiced Price) | Specifies, in the local currency, the total billable price for the project task that has been invoiced during the time period in the Posting Date Filter field. | |
| Remaining (Total Cost) | Remaining (Total Cost) | Specifies the remaining total cost (LCY) as the sum of costs from project planning lines associated with the project task. The calculation occurs when you have specified that there is a usage link between the project ledger and the project planning lines. | |
| Remaining (Total Price) | Remaining (Total Price) | Specifies the remaining total price (LCY) as the sum of prices from project planning lines associated with the project task. The calculation occurs when you have specified that there is a usage link between the project ledger and the project planning lines. | |
| EAC (Total Cost) | Rec.CalcEACTotalCost() |
Specifies the estimate at completion (EAC) total cost for a project task line. If the Apply Usage Link check box on the project is selected, then the EAC (Total Cost) field is calculated as follows: Usage (Total Cost) + Remaining (Total Cost). | |
| EAC (Total Price) | Rec.CalcEACTotalPrice() |
Specifies the estimate at completion (EAC) total price for a project task line. If the Apply Usage Link check box on the project is selected, then the EAC (Total Price) field is calculated as follows: Usage (Total Price) + Remaining (Total Price). | |
| Global Dimension 1 Code | Global Dimension 1 Code | Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. from the table field | |
| Global Dimension 2 Code | Global Dimension 2 Code | Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. from the table field | |
| External Document No. | External Document No. | Specifies a document number that refers to the customer’s or vendor’s numbering system. | |
| Your Reference | Your Reference | Specifies the customer’s reference. The content will be printed on sales documents. | |
| Outstanding Orders | Outstanding Orders | Specifies the sum of outstanding orders, in local currency, for this project task. The value of the Outstanding Amount (LCY) field is used for entries in the Purchase Line table of document type Order to calculate and update the contents of this field. from the table field | |
| Amt. Rcd. Not Invoiced | Amt. Rcd. Not Invoiced | Specifies the sum for items that have been received but have not yet been invoiced. The value in the Amt. Rcd. Not Invoiced (LCY) field is used for entries in the Purchase Line table of document type Order to calculate and update the contents of this field. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Project Task | Project Planning Lines | View all planning lines for the project. You use this window to plan what items, resources, and general ledger expenses that you expect to use on a project (budget) or you can specify what you actually agreed with your customer that he should pay for the project (billable). | |
| Assigned Resources | View or edit the additional resources that are explicitly assigned to this project task. Project-level assignments are managed from the project and are not shown on the project tasks. | ||
| Statistics | View statistics for the project task. | Page 1024 “Job Task Statistics” | |
| Dimensions | Dimensions-Single | View or edit the single set of dimensions that are set up for the selected record. | Page 1005 “Job Task Dimensions” |
| Dimensions-Multiple | View or edit dimensions for a group of records. You can assign dimension codes to transactions to distribute costs and analyze historical information. | ||
| Documents | Create Sales Invoice | Use a batch job to help you create sales invoices for the involved project tasks. | |
| Sales Invoices/Credit Memos | View sales invoices or sales credit memos that are related to the selected project task. | ||
| History | Project Ledger Entries | View the project ledger entries. | Page 92 “Job Ledger Entries” |
| Functions | Split Planning Lines | Split planning lines of type Budget and Billable into two separate planning lines: Budget and Billable. | |
| Change Dates | Use a batch job to help you move planning lines on a project from one date interval to another. | ||
| Indent Project Tasks | Move the selected lines in one position to show that the tasks are subcategories of other tasks. Project tasks that are totaled are the ones that lie between one pair of corresponding Begin-Total and End-Total project tasks. | Codeunit 1003 “Job Task-Indent” | |
| Copy | Copy Project Planning Lines from… | Use a batch job to help you copy planning lines from one project task to another. You can copy from a project task within the project you are working with or from a project task linked to a different project. | |
| Copy Project Planning Lines to… | Use a batch job to help you copy planning lines from one project task to another. You can copy from a project task within the project you are working with or from a project task linked to a different project. | ||
| WIP | Calculate WIP | Run the Project Calculate WIP batch job. | |
| Post WIP to G/L | Run the Project Post WIP to G/L batch job. |
Events published
OnBeforeOnActionJobPlanningLines(var JobTask: Record "Job Task"; var IsHandled: Boolean)(integration)OnBeforeOnDrillDownOutstandingOrders(var JobTask: Record "Job Task"; var IsHandled: Boolean)(integration)OnBeforeOnDrillDownAmtRcdNotInvoiced(var JobTask: Record "Job Task"; var IsHandled: Boolean)(integration)
Procedures
SetPerTaskBillingFieldsVisible(Visible: Boolean)+ BC24
Triggers
OnAfterGetRecord, OnNewRecord
Relations
- card page Page 1003 “Job Task Card”
- source table Table 1001 “Job Task”
Extended by
Recent changes
- 2026-07-14 #9315 [Projects] Add Assigned Resources to projects and project tasks (main, BC30, feature)
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "page", object_name: "Job Task Lines Subform"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.