Page 463 "Jobs Setup"
Base Application · Microsoft.Projects.Project.Setup
Across versions
- BC23present
- BC24declaration changed
- BC25-30unchanged
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.Projects.Project.Setup · captioned “Projects Setup” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Projects Setup |
| SourceTable | Jobs Setup |
| PageType | Card |
| UsageCategory | Administration |
| ApplicationArea | Jobs |
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 |
|---|---|---|---|
| General | Automatic Update Job Item Cost | Automatic Update Job Item Cost | Specifies in the Projects Setup window that cost changes are automatically adjusted each time the Adjust Cost - Item Entries batch job is run. The adjustment process and its results are the same as when you run the Update Project Item Cost batch job. from the table field |
| Apply Usage Link by Default | Apply Usage Link by Default | Specifies whether project ledger entries are linked to project planning lines by default. Select this check box if you want to apply this setting to all new projects that you create. from the table field | |
| Allow Budget/Billable Lines Def | Allow Sched/Contract Lines Def | Specifies whether project lines can be of type Both Budget and Billable by default. Select this check box if you want to apply this setting to all new projects that you create. from the table field | |
| Default WIP Method | Default WIP Method | Specifies the default method to be used for calculating work in process (WIP). It is applied whenever you create a new project, but you can modify the value on the project card. from the table field | |
| Default WIP Posting Method | Default WIP Posting Method | Specifies how the default WIP method is to be applied when posting Work in Process (WIP) to the general ledger. By default, it is applied per project. from the table field | |
| Default Job Posting Group | Default Job Posting Group | Specifies the default posting group to be applied when you create a new project. This group is used whenever you create a project, but you can modify the value on the project card. from the table field | |
| Default Task Billing Method | Default Task Billing Method | Specify whether to use the customer specified for the project for all tasks or allow people to specify different customers. One customer lets you invoice only the customer specified for the project. Multiple customers lets you invoice customers specified on each task, which can be different customer… from the table field | |
| Logo Position on Documents | Logo Position on Documents | Specifies the position of your company logo on business letters and documents. from the table field | |
| Document No. Is Job No. | Document No. Is Job No. | Specifies that the project number is also the document number in the ledger entries posted for the project. from the table field | |
| Prices | Default Sales Price List Code | Default Sales Price List Code | Specifies the code of the existing sales price list that stores all new price lines created in the price worksheet page. from the table field |
| Default Purch Price List Code | Default Purch Price List Code | Specifies the code of the existing purchase price list that stores all new price lines created in the price worksheet page. from the table field | |
| Numbering | Job Nos. | Job Nos. | Specifies the code for the number series that will be used to assign numbers to projects. To see the number series that have been set up in the No. Series table, click the drop-down arrow in the field. from the table field |
| Job WIP Nos. | Job WIP Nos. | Specifies the code for the number series that will be used to assign numbers to project WIP documents. To see the number series that have been set up in the No. Series table, click the drop-down arrow in the field. from the table field | |
| Price List Nos. | Price List Nos. | Specifies the code for the number series that will be used to assign numbers to project price lists. from the table field | |
| Archiving | Archive Orders | Archive Jobs | Specifies if you want to automatically archive projects when: deleted, status changed, when project or project task quote sent to customer or related sales invoice posted. from the table field |
Triggers
OnOpenPage
Relations
- source table Table 315 “Jobs Setup”
Pages and codeunits on this table
- Table 315 “Jobs Setup” (drill-down page)
- Table 315 “Jobs Setup” (lookup page)
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 7001 “Price Calculation Mgt.” (1 call:
OnOpenPage → IsExtendedPriceCalculationEnabled)
Documented on Microsoft Learn
- Set up projects, prices, and project posting groups
- Project management
- Set Up Resources, Time Sheets, and Projects
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). The call sections above are our own, per object, from the BC29 call graph. 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: "Jobs Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.