Page 6711 "OData Setup Wizard"
Base Application · System.Integration
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · System.Integration · captioned “Reporting Data Setup” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Reporting Data Setup |
| SourceTable | Tenant Web Service |
| PageType | NavigatePage |
| UsageCategory | Administration |
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 |
|---|---|---|---|
| Control17 | MediaResourcesStandard.““Media Reference”” | MediaResourcesStandard."Media Reference" |
— |
| Control19 | MediaResourcesDone.““Media Reference”” | MediaResourcesDone."Media Reference" |
— |
| Welcome to Reporting Data Setup | You can create data sets that you can use for building reports in Excel, Power BI, or any other reporting tool that works with an OData data source. | label | — |
| Whitespace1.1.1 | label | — | |
| For some tools such as Power BI, selecting columns or setting filters from this assisted setup guide will have no effect. After you complete the assisted setup, use Power BI Desktop to create or modify reports to use the newly created web service, selecting the columns and setting the filters as nee… | label | — | |
| Let’s go! | Choose Next so you can create reporting data sets. | label | — |
| I want to… | ActionType | ActionType |
— |
| Control28 | Name | ServiceNameLookup |
— |
| Control32 | New Name | ServiceNameEdit |
Specifies the service name. Name cannot contain space(s). |
| Select the data you would like to use for your reports and define a name for this data set. | Data Source Type | ObjectTypeLookup |
— |
| Data Source Id | Rec."Object ID" |
— | |
| Data Source Name | DisplayObjectName() |
— | |
| Choose the Fields to include in your data set | ODataColSubForm | part Page 6710 “OData Column Choose SubForm” | — |
| Success! | Your data set has been successfully created! | label | — |
| OData URL | oDataUrl |
— |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Add Filters | — | |
| Back | — | ||
| Next | — | ||
| Publish | — | ||
| Finish | — | ||
| Excel | — |
Procedures
ConvertFieldTypeToEdmType(FieldType: FieldType): Enum "Edit in Excel Edm Type"EditInExcelVisible()
Plus 14 local procedures.
Triggers
OnInit, OnOpenPage, OnQueryClosePage
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 6710 “ODataUtility” (6 calls:
CopyTempTableToConcreteTable → GenerateODataV3FilterText,CopyTempTableToConcreteTable → GenerateODataV4FilterText,CopyTempTableToConcreteTable → GenerateSelectText, …) - Codeunit 9750 “Web Service Management” (6 calls:
CopyTempTableToConcreteTable → SetODataFilterClause,CopyTempTableToConcreteTable → SetODataSelectClause,CopyTempTableToConcreteTable → SetODataV4FilterClause, …) - Codeunit 4030 “Client Type Management” (2 calls:
EditInExcelVisible → GetCurrentClientType,LoadTopBanners → GetCurrentClientType) - Codeunit 1490 “Edit in Excel Filters” (1 call:
UpdateEditInExcelFilters → AddFieldV2)
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: "OData Setup Wizard"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.