Table 1620 "Office Document Selection"
Base Application · Microsoft.CRM.Outlook
Across versions
- BC23present
- BC24declaration changed
- BC25-27unchanged
- BC285 fields changed
- BC29-30unchanged
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.CRM.Outlook · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Office Document Selection |
| 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 | Series Δ BC28 | Option | Specifies the series of the involved document, such as Purchasing or Sales. | OptionCaption: Sales,Purchase |
| 2 | Document Type Δ BC28 | Enum “Incoming Document Type” | Specifies the document type that the entry belongs to. | enum Enum 133 “Incoming Document Type” |
| 3 | Document No. Δ BC28 | Code[20] | Specifies the number of the involved document. | |
| 4 | Posted Δ BC28 | Boolean | Specifies whether the involved document has been posted. | |
| 5 | Document Date Δ BC28 | Date | Specifies the date when the related document was created. |
Keys
- Key1: Series, Document Type, Document No., Posted (clustered)
Pages and codeunits on this table
- Page 1602 “Office Document Selection” (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 Document Selection"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.