Table 8360 "Financial Report Schedule"
Base Application · Microsoft.Finance.FinancialReports
Across versions
- BC23-27not present
- BC28added
- BC291 fields changed
- BC30unchanged
Neighbourhood 11 connected objects and pages
Base Application · Microsoft.Finance.FinancialReports · BC28-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Financial Report Schedule |
| DataClassification | CustomerContent |
| LookupPageId | Financial Report Schedules |
| DrillDownPageId | Financial Report Schedules |
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 | Financial Report Name | Code[10] | Specifies the name of the financial report. | TableRelation Table 88 “Financial Report” (Financial Report); NotBlank |
| 2 | Code | Code[20] | Specifies the code of the schedule. | NotBlank |
| 3 | Description | Text[100] | Specifies the description. | |
| 4 | Export to Excel | Boolean | Specifies if the report will be exported to Excel. | |
| 5 | Export to PDF | Boolean | Specifies if the report will be exported to PDF. | |
| 6 | Excel Template Code | Code[20] | Specifies the Excel template used when exporting to Excel. If not specified, the template on the financial report definition is used instead. | TableRelation Table 764 “Fin. Report Excel Template” (“Fin. Report Excel Template”.Code where(“Financial Report Name” = field(“Financial Report Name”))) |
| 7 | Send Email Δ BC29 | Boolean | Specifies if the exported Excel or PDF file will be sent to the recipients via email. You can specify who will receive the email in Financial Report Recipients. | |
| 8 | Next Run Date/Time | DateTime | Specifies the next date and time this schedule will run. | |
| 9 | Recurrence Run Date Formula | DateFormula | Specifies the date formula that is used to calculate the next time this schedule will run. For example use CM+1M to run the report at the end of every month. | |
| 10 | Expiration Date/Time | DateTime | Specifies the date and time when the schedule is to expire, after which the schedule will not be run. | |
| 11 | Report Filters | Blob | Specifies the filters used when exporting this schedule to Excel. | |
| 12 | Report Parameters | Blob | Specifies the parameters used when exporting this schedule to PDF. | |
| 13 | Financial Report Row Group | Code[10] | — | TableRelation Table 84 “Acc. Schedule Name” (Acc. Schedule Name) |
| 14 | Financial Report Column Group | Code[10] | — | TableRelation Table 333 “Column Layout Name” (Column Layout Name) |
| 15 | Start Date Filter Formula | DateFormula | Specifies the date formula used to automatically calculate the start date of the report date filter. If not specified, the value on the financial report definition is used instead. | |
| 16 | End Date Filter Formula | DateFormula | Specifies the date formula used to automatically calculate the end date of the report date filter. If not specified, the value on the financial report definition is used instead. | |
| 17 | Date Filter Period Formula | Code[20] | Specifies the period formula used to automatically calculate the report date filter. If not specified, the value on the financial report definition is used instead. | |
| 18 | Date Filter Period Formula LID | Integer | Specifies the period formula language ID. | |
| 19 | No. of Recipients | Integer | Specifies the number of recipients that will receive the financial report. | FlowField: count(“Financial Report Recipient” where(“Financial Report Name” = field(“Financial Report Name”), “Financial Report Schedule Code” = field(Code))); not editable |
| 20 | Custom Filters | Boolean | Specifies if the schedule will export the PDF and Excel reports with custom filters. Uncheck this field to clear the custom filters. If not specified, the filters on the financial report definition is used instead. |
Keys
- PK: Financial Report Name, Code (clustered)
- NextRunDateTime: Next Run Date/Time
Trigger event subscribers
- OnAfterInsertEvent: Codeunit 8360 “Financial Report Export” FinancialReportScheduleOnAfterInsert
- OnAfterModifyEvent: Codeunit 8360 “Financial Report Export” FinancialReportScheduleOnAfterModify
Procedures
CalcNextRunDate()EditCustomFilters()SetCustomFilters()GetReportParameters(): TextSetReportParameters(TextValue: Text)GetReportFilters(): TextSetReportFilters(TextValue: Text)
Plus 1 local procedures.
Triggers
OnDelete
Relations
- drill-down page Page 8360 “Financial Report Schedules”
- lookup page Page 8360 “Financial Report Schedules”
- Financial Report Column Group: TableRelation Table 333 “Column Layout Name”
- Excel Template Code: TableRelation Table 764 “Fin. Report Excel Template”
- No. of Recipients: CalcFormula Table 8362 “Financial Report Recipient”
- Financial Report Row Group: TableRelation Table 84 “Acc. Schedule Name”
- Financial Report Name: TableRelation Table 88 “Financial Report”
Referenced by
2 fields in 2 objects relate to this table (TableRelation or CalcFormula).
- Table 8361 “Financial Report Export Log”: Financial Report Schedule Code
- Table 8362 “Financial Report Recipient”: Financial Report Schedule Code
Pages and codeunits on this table
- Page 8360 “Financial Report Schedules” (source table)
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 18 “Financial Report Mgt.” (1 call:
EditCustomFilters → SetAccScheduleFilter) - Codeunit 28 “Error Message Management” (1 call:
ValidateRecipientEmails → CollectErrors)
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: "table", object_name: "Financial Report Schedule"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.