Table 5579 "Digital Voucher Entry Setup"
EnforcedDigitalVouchers · Microsoft.EServices.EDocument
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
EnforcedDigitalVouchers · Microsoft.EServices.EDocument · BC29-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 5579 “Digital Voucher Entry Setup” (2 Learn pages).
Properties
| Property | Value |
|---|---|
| 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 | Entry Type | Enum “Digital Voucher Entry Type” | Specifies the entry type. via Page 5579 “Digital Voucher Entry Setup” | enum Enum 5579 “Digital Voucher Entry Type”; NotBlank |
| 2 | Check Type | Enum “Digital Voucher Check Type” | Specifies the check type. via Page 5579 “Digital Voucher Entry Setup” | enum Enum 5580 “Digital Voucher Check Type” |
| 3 | Generate Automatically | Boolean | Specifies if the digital voucher needs to be generated automatically. via Page 5579 “Digital Voucher Entry Setup” | |
| 4 | Skip If Manually Added | Boolean | Specifies if the automatically generated digital voucher do not to be added to the document even if the manual attachment has already been added. via Page 5579 “Digital Voucher Entry Setup” | |
| 5 | Consider Blank Doc. Type | Boolean | Specifies if the blank document type is considered for the entry type. This option is only available for the General Journal, Sales Journal and Purchase Journal. via Page 5579 “Digital Voucher Entry Setup” |
Keys
- PK: Entry Type (clustered)
Pages and codeunits on this table
- Page 5579 “Digital Voucher Entry Setup” (source table)
Recent changes
- 2026-08-11 #9208 [Enforced Digital Vouchers] - Attaching EDocuments when using Digital Vouchers (main, BC30, feature)
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: "Digital Voucher Entry Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.