Page 7110 "Analysis Types"
Base Application · Microsoft.Inventory.Analysis
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Inventory.Analysis · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Analysis Types |
| SourceTable | Analysis Type |
| PageType | List |
| UsageCategory | Administration |
| ApplicationArea | SalesAnalysis, PurchaseAnalysis, InventoryAnalysis |
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 | Code | Code | Specifies the code of the analysis type. from the table field |
| Name | Name | Specifies a description of the analysis type. from the table field | |
| Value Type | Value Type | Specifies the value type that the analysis type is based on. from the table field | |
| Item Ledger Entry Type Filter | Item Ledger Entry Type Filter | Specifies a filter on the type of item ledger entry. from the table field | |
| Value Entry Type Filter | Value Entry Type Filter | Specifies a filter on the type of item value entry. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Reset Default Analysis Types | Revert to use the default analysis types that exist in the system. |
Procedures
2 local procedures, no public ones.
Triggers
OnAfterGetRecord
Relations
- source table Table 7113 “Analysis Type”
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 7110 “Analysis Report Management” (2 calls:
ItemLedgerEntryTypeFilterOnFor → ValidateFilter,ValueEntryTypeFilterOnFormat → ValidateFilter)
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: "Analysis Types"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.