Page 360 "Document Sending Profile"
Base Application · Microsoft.Foundation.Reporting
Across versions
- BC23-30present
Neighbourhood 7 connected objects and pages
Base Application · Microsoft.Foundation.Reporting · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Document Sending Profile |
| SourceTable | Document Sending Profile |
| PageType | Card |
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 | Code | Code | Specifies a code to identify the document sending method in the system. from the table field |
| Description | Description | Specifies the document sending format. from the table field | |
| Default | Default | Specifies if this document sending method will be used as the default method for all customers. from the table field | |
| Sending Options | Printer | Printer | Specifies if and how the document is printed when you choose the Post and Send button. If you choose the Yes (Prompt for Settings) option, the document is printed according to settings that you must make on the printer setup dialog. from the table field |
| Specifies if and how the document is attached as a PDF file to an email to the involved customer when you choose the Post and Send button. If you choose the Yes (Prompt for Settings) option, the document is attached to an email according to settings that you must make in the Send Email window. from the table field | |||
| Control15 | E-Mail Attachment | E-Mail Attachment | Specifies the type of file to attach. from the table field |
| Control16 | Format | E-Mail Format | Specifies how customers are set up with their preferred method of sending sales documents. from the table field |
| Control19 | Combine PDF Documents | Combine Email Documents | Merge selected documents into a single PDF file when you send the documents by email or print them. For example, this reduces the number of documents the recipient must process. from the table field |
| Sending Options | Disk | Disk | Specify if the document is saved as a PDF file when you choose the Post and Send button. from the table field |
| Control17 | Format | Disk Format | Specifies how customers are set up with their preferred method of sending sales documents. |
| Sending Options | Electronic Document | Electronic Document | Specifies if the document is sent as an electronic document that the customer can import into their system when you choose the Post and Send button. To use this option, you must also fill the Electronic Format field. Alternatively, the file can be saved to disk. from the table field |
| Control18 | Format | Electronic Format | Specifies which format to use for electronic document sending. You must fill this field if you selected the Silent option in the Electronic Document field. from the table field |
Procedures
LookupElectronicFormat(var ElectronicFormat: Code[20])GetFormat(): Code[20]
Triggers
OnOpenPage
Relations
- source table Table 60 “Document Sending Profile”
Pages and codeunits on this table
- Page 359 “Document Sending Profiles” (card page)
Extended by
Documented on Microsoft Learn
- Set up the E-Documents connector with external endpoints
- Set Up E-documents
- Set up electronic invoicing with NemHandel
- Electronic invoicing in Norway
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: "Document Sending Profile"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.