Chart processing method and device, electronic equipment, storage medium and program product

Abstract

The present application provides a chart processing method, device, electronic equipment, storage medium and program product. The method comprises receiving a first operation, the first operation being used for configuring a plurality of hierarchical fields and chart types corresponding to the hierarchical fields for a chart component in a first table, the hierarchical fields being created fields in the first table; in response to a second operation, displaying a first chart in the chart component, the first chart being created based on data records of the first table and having a first data dimension corresponding to a first hierarchical field and a first chart type; in response to a third operation, displaying a second chart in the chart component, the second chart being created based on the data records of the first table and having a second data dimension corresponding to a second hierarchical field and a second chart type, the first hierarchical field being a first field in the first table, and the second hierarchical field being a second field in the first table. The method solves the problems of low data display efficiency and limited analysis dimension of the online table.

Description

Technical Field

[0001] This article relates to the field of computer processing technology, and in particular to a chart processing method, apparatus, electronic device, storage medium, and program product. Background Technology

[0002] Online spreadsheets, supporting real-time collaborative editing by multiple users, have become a mainstream tool for daily office work and data collaboration. With the widespread use of online spreadsheets and data visualization tools, the demand for in-depth analysis of high-frequency dynamic data continues to grow. However, existing online spreadsheets suffer from low data exploration efficiency and limited analytical dimensions, failing to meet the needs for flexible and in-depth visualization analysis. Summary of the Invention

[0003] This paper provides a chart processing method, device, electronic device, storage medium, and program product to solve the problems of low data display efficiency and limited analytical dimensions in online tables.

[0004] In one scenario, this paper provides a chart processing method, which includes: Receive a first operation, the first operation being configured to configure multiple hierarchical fields and chart types corresponding to the hierarchical fields for a chart component in a first table, wherein the hierarchical fields are fields already created in the first table; In response to the second operation, a first chart is displayed in the chart component. The first chart is created based on the data records of the first table and has a first data dimension and a first chart type corresponding to the first level field. In response to the third operation, a second chart is displayed in the chart component. The second chart is created based on the data records of the first table and has a second data dimension and a second chart type corresponding to the second-level field. The first-level field is the first field in the first table, and the second-level field is the second field in the first table.

[0005] In one instance, this document also provides a chart processing apparatus, the apparatus comprising: A receiving module is used to receive a first operation, the first operation being used to configure multiple hierarchical fields and chart types corresponding to the hierarchical fields for a chart component in a first table, wherein the hierarchical fields are fields that have been created in the first table; A first display module is configured to respond to a second operation by displaying a first chart in the chart component. The first chart is created based on the data records of the first table and has a first data dimension and a first chart type corresponding to the first level field. The second display module is used to display a second chart in the chart component in response to a third operation. The second chart is created based on the data records of the first table and has a second data dimension and a second chart type corresponding to a second-level field. The first-level field is the first field in the first table, and the second-level field is the second field in the first table.

[0006] In one instance, this document also provides an electronic device comprising: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the graph processing method as described herein.

[0007] In one instance, this document also provides a storage medium containing computer-executable instructions that, when executed by a computer processor, are used to perform the graph processing methods described herein.

[0008] In another scenario, this document also provides a computer program product, including a computer program that, when executed by a processor, implements the graph processing methods as described herein.

[0009] In the above method, receiving the first operation allows configuration of multiple hierarchical fields and corresponding chart types for the chart component in the first table. This enables the sequential display of charts corresponding to different hierarchical fields based on these fields and their corresponding chart types. This allows for flexible switching between different data dimensions and chart display formats within the same chart component, eliminating the need for complex configuration operations and enabling rapid switching of data display dimensions and granularity, significantly simplifying the chart visualization configuration process. The second operation displays the first chart within the chart component. This first chart is generated based on existing data records in the first table and possesses a first data dimension and first chart type matching the first hierarchical field. It can automatically complete the visualization rendering of the target dimension data, accurately presenting the first data dimension corresponding to the first hierarchical field. The proposed solution enables rapid visualization of single data dimensions, ensuring the immediacy and relevance of data presentation. Furthermore, it responds to third operations by seamlessly switching to a second chart within the same chart component. This second chart, also generated from the existing data records of the first table, possesses a second data dimension and chart type matching the second-level fields. This allows for rapid presentation of visualization results corresponding to the second-level fields without the need to create new charts or reload the data source, achieving seamless switching between different data analysis dimensions. This solution effectively overcomes the inherent limitations of charts, such as single analytical dimensions and cumbersome dimension switching processes, improving the efficiency of online table data exploration and multidimensional data analysis, and resolving the issues of complex data display dimension switching operations and insufficient data analysis flexibility. Attached Figure Description

[0010] The above and other features, advantages, and aspects of the embodiments described herein will become more apparent when taken in conjunction with the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0011] Figure 1 This is a schematic diagram of the structure of a chart processing system under one scenario. Figure 2 This is a flowchart illustrating a chart processing method for one scenario. Figure 3 This is a schematic diagram illustrating the configuration of multiple levels of fields in a chart component of an online table in one scenario. Figure 4 This is a schematic diagram illustrating the configuration of multiple hierarchical fields for a chart component in an online table, in another scenario. Figure 5 This is a schematic diagram of the hierarchical fields of a chart component in an online table, representing one scenario. Figure 6This is a diagram illustrating the hierarchical fields of a chart component in an online table, in another scenario. Figure 7 This is a schematic diagram of breadcrumb structure when displayed in a chart in an online table under one specific scenario. Figure 8 This is a schematic diagram of a chart processing device in one scenario. Figure 9 This is a schematic diagram of the structure of an electronic device that implements a graph processing method in one scenario. Detailed Implementation

[0012] The embodiments will now be described in more detail with reference to the accompanying drawings. While some embodiments are shown in the drawings, it should be understood that the technical solution can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present technical solution. It should be understood that the illustrated drawings and embodiments are for illustrative purposes only and are not intended to limit the scope of protection of the technical solution.

[0013] It should be understood that the steps described in the method implementation may be performed in different orders and / or in parallel. Furthermore, the method implementation may include additional steps and / or omit the steps shown. The scope of this document is not limited in this respect.

[0014] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one situation" means "at least one situation"; the term "another situation" means "at least one additional situation"; the term "some situations" means "at least some situations". Definitions of other terms will be given in the following description.

[0015] It should be noted that the concepts of "first" and "second" mentioned in this article are only used to distinguish different devices, modules or units, and are not used to limit the order of the functions performed by these devices, modules or units or their interdependencies.

[0016] It should be noted that the terms "one" and "more" used in this document are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0017] The names of messages or information exchanged between multiple devices in this document are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0018] It is understood that before using the technical solutions disclosed in the various embodiments of this document, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this document in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0019] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as electronic devices, applications, servers, or storage media, that perform the operations described herein, based on the prompt message.

[0020] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0021] It is understood that the above notification and user authorization process is merely illustrative and does not limit the implementation method described in this article. Other methods that comply with relevant laws and regulations may also be applied to the implementation method described in this article.

[0022] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0023] The technical solution in this article can be applied to... Figure 1 The diagram illustrates a chart processing system. In practical applications, this chart processing system may include a client 101 and a server 102. The client 101 may include, but is not limited to, browsers, applications (Apps), Hyper Text Markup Language (HTML) applications, lightweight applications (also known as mini-programs), or cloud applications. The client 101 may be deployed on an electronic device, relying on the operation of that device or certain applications within the device to implement its functions. The electronic device may be, for example, a device with a display screen that supports information browsing, such as a smartphone, tablet, personal computer, or other client terminal. For ease of understanding, Figure 1The client is primarily represented by a device. Other applications, such as chart processing applications, can also be configured on the electronic device. Server 102 can be one or more servers providing various services. That is, it can be implemented as a distributed server cluster composed of multiple servers, or as a single server; furthermore, it can be a server for a distributed system, a server integrating blockchain technology, a cloud server, or an intelligent cloud computing server or intelligent cloud host deployed with machine learning models, etc.

[0024] It should be noted that in this technical solution, the chart processing method can be executed by client 101, or by client 101 and server 102, with different functional parts of the corresponding chart processing device deployed on client 101 and server 102 respectively; wherein, the first processing module, second processing module, and third processing module of the device are deployed on client 101. It should be understood that... Figure 1 The number of clients and servers shown is for illustrative purposes only. Any number of clients and servers can be configured to meet specific implementation requirements.

[0025] Figure 2 A flowchart illustrating a chart processing method is provided for a specific scenario. This method is applicable to scenarios where different data dimensions and chart display formats within the same chart component of an online table can be flexibly switched. The chart processing method can be executed by a chart processing device, which can be implemented in software and / or hardware, optionally through an electronic device such as a mobile terminal, PC, or server. Figure 2 As shown, the chart processing methods in this article may specifically include the following processes: S210. Receive the first operation, which is used to configure multiple hierarchical fields and chart types corresponding to the hierarchical fields for the chart component in the first table. The hierarchical fields are fields that have been created in the first table.

[0026] See Figure 3 and Figure 4The first table 31 can be an online table that supports collaborative editing by at least two users, providing raw table data for charts. During or after the creation of the first table, user information and operation permissions for accessing and editing the first table can be configured. For example, users with a certain permission level can be granted access and editing permissions to the first table, and users meeting that permission level can act as collaborating users. Interactive operations in the first table can include: inserting cells, inserting row data, inserting column data, deleting data, modifying cell data, adding filter conditions, and deleting filter conditions. Operations such as inserting cells, inserting row data, inserting column data, deleting data, and modifying cell data can adjust the data content in the first table; adding and deleting filter conditions can adjust the view state of the first table.

[0027] The first table is an online table that supports collaborative editing by at least two users. The chart component within the first table is embedded in the visualization module that links the first table to its data source. It is used to present and display data in chart form based on existing fields, data records, and data structure within the first table. Optionally, the first operation may include an editing operation triggered by at least one of the following interaction methods: page interactive controls, menu options, or drag-and-drop configuration, to configure multiple hierarchical fields and the corresponding chart types for the chart component in the first table.

[0028] See Figure 3 and Figure 4 The first interactive area 310 can be an interactive area displayed in the first table 31 for configuring hierarchical fields and corresponding chart types for the chart components of the first table. For example, the first interactive area can be presented in the first table 31 in at least one form, such as a pop-up window, dialog box, overlay, drop-down menu, or tooltip. By providing configuration entries for hierarchical fields and corresponding chart types in the first interactive area displayed in the first table, the first interactive area supports the creation, editing, or maintenance of hierarchical fields and corresponding chart types. The chart components of the first table are displayed in the second interactive area 320 of the first table.

[0029] See Figure 3 and Figure 4The chart component in the first table can have multiple hierarchical fields, which can be pre-created fields within the table. These hierarchical fields are pre-configured to correspond to different data display dimensions or data grouping dimensions, providing the chart component with multiple sets of switchable data dimension bases. Different hierarchical fields correspond to different data statistics, display, or analysis dimensions. By configuring multiple hierarchical fields for the chart component in the first table, it is possible to perform data statistics and visualization based on different dimensions of the same data source, thereby achieving flexible switching of data display dimensions.

[0030] See Figure 3 and Figure 4 The first operation can be an editing operation performed within the first interactive area 310 to create, edit, and / or modify the hierarchy fields and corresponding chart types for the chart components of the first table. For example, the first operation can be an operation to create, edit, drag and / or add hierarchy fields and corresponding chart types in the first interactive area, which can be implemented by clicking, dragging, or selecting.

[0031] In some cases, optionally, in response to a trigger operation received by a first control on the first table, a first interactive area is displayed on the first table. The first control can be a clickable and operable button, entry point, or switch configured on the first table, and is used to control the display or hiding of the first interactive area on the first table. The first interactive area displayed on the first table can be presented as a sidebar of the first table, or it can be presented as a hierarchical field configured in the chart component of the first table and the corresponding chart type.

[0032] The technical effect of the above solution is that it displays charts corresponding to different levels of fields and corresponding chart types in sequence, realizing flexible switching between different data dimensions and different chart display formats within the same chart component. It does not require complex configuration operations, and can quickly switch data display dimensions and data display granularity, greatly simplifying the chart visualization configuration process.

[0033] In some cases, it can be combined with the various options in one or more of the above cases. Multiple hierarchical fields correspond to hierarchical numbers, which are used to indicate the display level of each hierarchical field in the chart component of the first table; the chart type corresponding to the hierarchical field is used to indicate the chart display format of the corresponding display level.

[0034] See Figure 3 and Figure 4Each of the multiple hierarchical fields has a corresponding hierarchical number. This hierarchical number indicates the display level of each field within the chart component of the first table, identifying the arrangement order and hierarchical relationship of the fields. For example, the hierarchical number can be the numerical value corresponding to the field's level in the hierarchy. Setting hierarchical numbers for each field clearly identifies which field is the parent and which is the child, determining which data dimension to switch from when displaying the chart data.

[0035] See Figure 3 and Figure 4 The chart type corresponding to the hierarchical field is a pre-bound chart display style for the hierarchical field of the chart component in the first table. It indicates the visualization method to be used when the chart component in the first table displays data based on the data dimension corresponding to the hierarchical field. The display hierarchy corresponding to the hierarchical field can be the data display dimension corresponding to the hierarchical field used by the chart component in the first table. The chart display format can refer to specific chart visualization styles such as bar charts, line charts, pie charts, bar graphs, XY-axis charts, radar charts, word clouds, funnel charts, pivot tables, and leaderboards. By configuring the corresponding chart type for the hierarchical field, the visualization chart style rendered by the chart component when the hierarchical field is selected as the data display dimension can be directly determined. This eliminates the need to reset the chart type when switching data dimensions, thus achieving unified matching and rapid switching between data dimensions and chart display formats.

[0036] In some cases, it can be combined with the various optional solutions in one or more of the above cases. The chart processing method in this article also includes the following steps: in response to receiving a fifth operation on the chart component in the first table, displaying or hiding multiple hierarchical fields configured for the chart component in the first table and the chart types corresponding to the hierarchical fields. The fifth operation is used to control the enabling or disabling of the hierarchical field configuration function of the chart component in the first table.

[0037] See Figure 3 and Figure 4The first interactive area of ​​the first table contains a second control, which can be implemented as a button, switch, or option. This second control controls whether the configuration function of the hierarchy fields and corresponding chart types of the chart components in the first table is enabled. In response to a fifth operation, including when the second control in the first interactive area receives an enable operation, the first configuration content is displayed in the first interactive area. This first configuration content consists of the default hierarchy fields associated with the chart components in the first table and their corresponding default chart types. Alternatively, a sixth operation can be performed to configure the hierarchy fields and their corresponding chart types for the chart components in the first table. This sixth operation is a configuration operation received in the first table prior to the first operation. In response to a fifth operation, including when the second control in the first interactive area receives a disable operation, the first configuration content is hidden in the first interactive area.

[0038] See Figure 3 and Figure 4 The first interactive area 310 is used to display multiple hierarchical fields configured for the chart component of the first table and the corresponding chart types. As the page carrier for hierarchical field configuration, the first interactive area 310 provides a visual operation page area. A second control 330 can be set within the first interactive area 310 to control whether the hierarchical field configuration function is enabled within the first interactive area 310. For example, the second control 330 can be a switch or a button. Receiving an "enable" operation on the second control refers to an operation performed on the second control 330 to enable the hierarchical field configuration function within the first interactive area 310, thus causing the first interactive area to enter the hierarchical field configuration state. Receiving a "close" operation on the second control refers to an operation performed on the second control to close the hierarchical field configuration function, thus allowing the first interactive area to exit the hierarchical field configuration state.

[0039] The technical effect of the above solution is that by opening and closing the second control in the first interactive area, the configuration content corresponding to the chart component can be flexibly displayed or hidden. It can directly present the default hierarchical field configuration result or the previously saved hierarchical field configuration result without repeated settings, simplifying the configuration process of chart dimensions and chart types, improving the convenience of configuration operations, and enhancing the flexibility and operational efficiency of chart visualization configuration in online tables.

[0040] S220. In response to the second operation, display a first chart in the chart component of the first table. The first chart is created based on the data records of the first table and has a first data dimension and a first chart type corresponding to the first level field.

[0041] The second operation can be an operation on the chart component of the first table or a triggered operation to display the first chart. The chart component of the first table can be a functional component in the first table used for visualizing chart data, capable of generating and displaying corresponding charts based on the data records of the first table. The first-level field can be a data field that has been pre-configured for the chart component of the first table and belongs to the data field that has already been created in the first table. The first-level field is used to determine the data display dimension and data display granularity of the first data dimension corresponding to the data record of the first table when the chart is displayed.

[0042] The first data dimension can be a data statistics, grouping, and display dimension formed based on the first-level field. It is used to classify, group, and aggregate data records in the first table according to the second data dimension, thereby forming the data content displayed in the first chart. The first chart type can be a chart display format pre-bound to the first-level field, used to determine the corresponding visualization style when displaying chart data using the first data dimension corresponding to the first-level field. In response to the second operation, the first chart can be rendered and displayed in the chart component of the first table. The first chart is constructed using the existing data records in the first table as the data source, performs data summarization and statistics based on the first data dimension corresponding to the first-level field, and uses the pre-configured first chart type for visualization.

[0043] The technical effect of the above solution is that the first chart can be displayed in the chart component through the second operation. The first chart is generated based on the data records of the first table, and has a first data dimension and a first chart type that match the first level field. It can automatically complete the visualization rendering of the target dimension data, accurately present the data visualization results under the first data dimension corresponding to the first level field, realize the rapid visualization display of a single data dimension, and ensure the immediacy of data display.

[0044] S230. In response to the third operation, a second chart is displayed in the chart component of the first table. The second chart is created based on the data records of the first table and has a second data dimension and a second chart type corresponding to the second-level field. The first-level field is the first field in the first table, and the second-level field is the second field in the first table.

[0045] The third operation can be an operation triggered by the chart component of the first table to switch the display of the second chart from the first chart. The second-level field can be a data field that has been pre-configured for the chart component of the first table and has been created in the first table. The second-level field is used to determine the data display dimension and data display granularity of the second data dimension corresponding to the data record of the first table when the chart is displayed.

[0046] The second data dimension can be a data statistics, grouping, and display dimension formed based on the second-level field. It is used to classify, group, and aggregate data records in the first table according to the second data dimension, thereby forming the data content displayed in the second chart. The second chart type can be a chart display format pre-bound to the second-level field, used to determine the corresponding visualization style when displaying chart data using the second data dimension corresponding to the second-level field. In response to the third operation, the second chart can be displayed in the chart component of the first table. The second chart is created based on the data records of the first table, uses the second data dimension corresponding to the second-level field for data grouping and statistics, and is visualized using the second chart type.

[0047] The first-level field is the first field in the first table, and the second-level field is the second field in the first table. The first field and the second field are different data fields in the first table, each corresponding to a different data display dimension, enabling the chart component of the first table to achieve multi-dimensional and multi-form data visualization based on different fields.

[0048] The technical effect of the above solution is that it can quickly switch to another data dimension and chart display style within the same chart component of the first table. The second chart is also generated based on the original data records of the first table, and has a second data dimension and second chart type that matches the second-level fields. There is no need to create a new chart or reload the data source, which realizes seamless switching and display of different data dimensions and improves the convenience and efficiency of multidimensional data visualization analysis.

[0049] In some cases, it can be combined with one or more of the above-mentioned alternatives, where the first chart type and the second chart type are different chart types. The chart type corresponding to the hierarchy field is based on the chart types that can be configured and generated based on the configuration fields in the data records of the first table. In other words, the chart type corresponding to the hierarchy field belongs to the set of chart types supported and renderable by the configuration fields contained in the data records of the first table. The chart type corresponding to the hierarchy field is selected from the range of allowed configurable chart types, rather than exceeding the chart types supported by the data records of the first table.

[0050] In some scenarios, the data used to construct the first chart can be combined with the data from multiple sub-tables, and / or the data used to construct the second chart can also be from multiple sub-tables; the sub-tables are data tables within the first table. The data sources for both the first and second charts are not limited to a single sub-table but can come from multiple sub-tables. These sub-tables, being data tables within the first table, enable the aggregation and visualization of data records across multiple sub-tables. As components of the first table, the sub-tables are used for data classification, storage, and management; multiple sub-tables collectively constitute the data source for the first table. By using data from multiple sub-tables as the basis for chart construction, the range of data sources for the charts can be expanded, improving the completeness and comprehensiveness of the data display, meeting the unified data analysis and visualization needs across sub-tables in online tables, and enhancing the applicability of data processing and display.

[0051] In some cases, the first operation can be combined with one or more of the above-mentioned alternative schemes and may include the following steps: receiving configuration information for the hierarchical fields and chart types of the first sub-table, and receiving configuration information for the hierarchical fields and chart types of the second sub-table.

[0052] During the initial operation, the system can receive hierarchical field configuration information and chart type configuration information corresponding to the first sub-table and the second sub-table, respectively. The hierarchical field and chart type configuration information received for the first and second sub-tables are independent of each other. Based on the data structure, data type, and data analysis requirements of each sub-table, the system can set hierarchical fields and corresponding chart types for chart visualization in both sub-tables. This allows different sub-tables to use configurations that match their data characteristics for chart display.

[0053] The technical effect of the above solution is that it enables independent configuration of hierarchical fields and chart types for different sub-tables within the first table, meeting the data characteristics and visualization needs of different sub-tables, improving the refinement and flexibility of chart configuration, facilitating the rapid generation of corresponding charts based on data from different sub-tables, and improving the adaptability and efficiency of online table cross-sub-table data visualization.

[0054] In some cases, optionally, the chart processing method in this document further includes the following steps: In response to a trigger operation on the data table identifier corresponding to the first sub-table, collapse and hide multiple hierarchical fields associated with the first sub-table and the chart types corresponding to the hierarchical fields configured in the chart component of the first table, or expand and display multiple hierarchical fields associated with the first sub-table and the chart types corresponding to the hierarchical fields configured in the chart component of the first table. In response to a trigger operation on the data table identifier corresponding to the second sub-table, collapse and hide multiple hierarchical fields associated with the second sub-table and the chart types corresponding to the hierarchical fields configured in the chart component of the first table, or expand and display multiple hierarchical fields associated with the second sub-table and the chart types corresponding to the hierarchical fields configured in the chart component of the first table.

[0055] The technical effect of the above solution is that by executing trigger operations on the data table identifiers corresponding to the first and second sub-tables respectively, it is possible to collapse, hide or expand the multiple hierarchical fields associated with each sub-table and the chart types corresponding to the hierarchical fields, thereby realizing the partitioning control and on-demand display of hierarchical fields of different sub-tables. This can effectively simplify the layout of the configuration interface and avoid mutual interference and messy stacking of configuration information of multiple sub-tables.

[0056] In some cases, it can be combined with one or more of the alternative solutions mentioned above. The chart processing method in this article also includes the following steps: In response to the first operation, which includes a first editing operation on the hierarchical field configuration control, the value of the hierarchical field is configured for the chart component in the first table; in response to the first operation, which includes a second editing operation on the chart type configuration control associated with the hierarchical field, the chart type corresponding to the hierarchical field is configured for the chart component in the first table.

[0057] See Figure 5 and Figure 6 The hierarchical field configuration control 340 is an interactive control provided by the chart component of the first table for selecting or setting hierarchical fields of the chart component. The hierarchical field configuration control 340 can be displayed as a dropdown list, supporting selection by expanding the dropdown list or searching by entering keywords. Specifically, the hierarchical field configuration control 340 can be at least one of the following: a dropdown selection box, a dropdown list box, an input box, a pop-up selection panel, and a pop-up window selection control. The first editing operation can be at least one of the following editing operations performed on the hierarchical field configuration control: selection, input, or confirmation. The first editing operation is used to edit the field value corresponding to the hierarchical field. The field value corresponding to the hierarchical field is a specific field selected from the already created fields in the first table, serving as the basis for the chart data dimension.

[0058] See Figure 5 and Figure 6The chart type configuration control 350 can be an interactive control associated with a hierarchical field to set the corresponding chart visualization style. The second editing operation can be an editing operation performed on the chart type configuration control 350 to select and switch chart types, used to determine the chart display format corresponding to the hierarchical field. For example, the chart display format corresponding to the hierarchical field can be a bar chart, line chart, pie chart, or area chart. The chart type configuration control 350 can be displayed in the form of a drop-down list. The chart type configuration control 350 supports expanding the drop-down list for selection, or entering keywords for search selection. For example, the chart type configuration control 350 can specifically be at least one of a drop-down selection box, a drop-down list box, an input box, a pop-up selection panel, and a pop-up window selection control. The chart type configuration control 350 can present chart type options for different chart types. The chart types corresponding to adjacent hierarchical fields in the multiple hierarchical fields configured for the chart component of the first table are different.

[0059] The technical effect of the above solution is that by performing editing operations on the hierarchical field configuration control and the chart type configuration control respectively, the field values ​​of the chart component and the corresponding chart type configuration can be accurately and independently completed. This achieves one-to-one binding of data dimensions and visualization display forms, avoids mutual interference between different hierarchical fields, simplifies the configuration process of chart visualization, and improves configuration efficiency and accuracy.

[0060] In some cases, this can be combined with the various options in one or more of the above scenarios. Among the multiple hierarchical fields configured for the chart component of the first table, if the first-level field is a hierarchical field of the first level, the field value corresponding to the first-level field is configured as the value of the first field. The value of the first field is the value of the category field of the first chart, or the value of the first field in a pivot table if the first chart is a pivot table. If the second-level field is a hierarchical field after the first level, the field value corresponding to the second-level field is configured as the value of the second field. The value of the second field is a non-numeric type field not used by the first chart or the multiple hierarchical fields configured for the chart component of the first table.

[0061] In some cases, optionally, the chart processing method in this document may further include the following steps: in response to a first operation including a triggered operation of adding a control to a hierarchy field, adding at least one new hierarchy field and a chart type corresponding to the hierarchy field to the chart component in the first table.

[0062] See Figure 5 and Figure 6A hierarchical field addition control 360 is set up for the multiple hierarchical fields configured for the chart component of the first table. The hierarchical field addition control 360 can be a button prompting "Add Hierarchical Field," used to append new hierarchical fields to the end of the multiple hierarchical fields configured for the chart component of the first table. The trigger operation for adding the hierarchical field control can be at least one of a click or a long press. When the hierarchical field addition control 360 is triggered, at least one new hierarchical field is added to the end of the multiple hierarchical fields configured for the chart component of the first table. Using the above method, hierarchical fields can be quickly added to the end of the multiple hierarchical fields configured for the chart component of the first table by triggering the hierarchical field addition control, achieving flexible expansion of hierarchical fields.

[0063] In some cases, optionally, the chart processing method in this document may further include the following steps: in response to receiving a hover operation on a third-level field of a chart component in the first table, displaying a deletion control for the hierarchical field associated with the third-level field; in response to triggering an operation on the deletion control for the hierarchical field associated with the third-level field, removing the chart type corresponding to the third-level field from the chart component in the first table; and in response to the existence of a hierarchical field in the next level of the third-level field, adjusting it to the hierarchical number of the multiple hierarchical fields configured in the chart component in the first table.

[0064] See Figure 5 and Figure 6 The third-level field is a non-first-level field among the multiple hierarchical fields configured for the chart component in the first table. It enables dynamic deletion of hierarchical fields, supports flexible adjustment of the hierarchical path, and prevents the entire hierarchical structure from becoming invalid due to accidental deletion of the first-level field by limiting deletion to non-first-level fields. Upon receiving a hover operation, a deletion control appears to the right of the third-level field. This control can be a delete button marked "X". Clicking the deletion control removes the third-level field from the multiple hierarchical fields configured for the chart component in the first table. The hierarchical number of all subsequent hierarchical fields in the multiple hierarchical fields configured for the chart component in the first table decreases by 1.

[0065] In some cases, optionally, the chart processing method in this document may further include the following steps: in response to receiving a hover operation on a fourth-level field of a chart component in a first table, displaying an icon control associated with the fourth-level field; in response to a drag operation on the icon control associated with the fourth-level field, adjusting the hierarchical order of multiple hierarchical fields configured in the chart component in the first table, and adjusting them to the hierarchical sequence number of multiple hierarchical fields configured in the chart component in the first table.

[0066] The technical effect of the above solution is that by hovering over the fourth-level field to display the associated icon control, and then by dragging the icon control, the hierarchical order and hierarchical number of multiple level fields in the chart component can be adjusted intuitively. The hierarchical order can be flexibly adjusted without complex configuration, which improves the convenience and intuitiveness of the hierarchical field configuration, ensures that the hierarchical order adjustment is efficient and accurate, and provides a reliable and orderly configuration foundation for the chart to switch and display according to the preset level.

[0067] In some cases, it can be combined with one or more of the above-mentioned alternative solutions. The first table is simultaneously associated with a first sub-table and a second sub-table. The first sub-table and the second sub-table are respectively associated with a set of multiple hierarchical fields configured in the chart component of the first table and the chart types corresponding to the hierarchical fields. The chart processing method in this article also includes the following steps: In response to a third editing operation on multiple hierarchical fields associated with the first sub-table, the multiple hierarchical fields associated with the second sub-table are adjusted according to the editing result of the third editing operation; wherein the third editing operation includes at least one of the following: adding at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table; deleting at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table; modifying the value of at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table; adjusting the chart type corresponding to at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table; adjusting the hierarchical order of at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table.

[0068] See Figure 4 and Figure 6 To ensure consistency in the hierarchical fields and corresponding chart types associated with the first and second sub-tables, adding, deleting, modifying chart types, and adjusting the hierarchical order of hierarchical fields in the first sub-table will automatically adjust the hierarchical fields and corresponding chart types in the second sub-table accordingly. The technical advantage of this solution is that editing the hierarchical fields associated with the first sub-table automatically adjusts the configuration of the hierarchical fields in the second sub-table, eliminating the need for separate, repetitive settings. It supports simultaneous effects for adding, deleting, modifying values, changing chart types, and adjusting hierarchical order, significantly reducing multi-sub-table configuration operations, improving configuration consistency and efficiency, and enhancing the synergy of multi-sub-table configurations.

[0069] In some cases, optionally, in response to a third operation, a second chart is displayed in the chart component of the first table, including the following steps: In response to a trigger operation received in the first information of the first chart, at least one operation option is displayed. When the first chart is not a pivot table, the first information includes a data range or data point selected from the first chart; when the first chart is a pivot table, the first information includes a row dimension field or column dimension field selected from the first chart. The at least one operation option includes an operation option for controlling the execution of a fourth operation, which is to switch from the first data dimension corresponding to the first-level field to the second data dimension corresponding to the second-level field to display the data records of the first table in a chart. The data display detail indicated by the first data dimension corresponding to the first-level field is lower than the data display detail indicated by the second data dimension corresponding to the second-level field. In response to a trigger operation on the operation option for controlling the execution of the fourth operation, a second chart is displayed in the chart component of the first table.

[0070] In some cases, it can be combined with one or more of the alternatives mentioned above to display a second chart in the chart component of the first table in response to the third operation. Specifically, this may include the following steps: Based on the first-level field of the first chart, obtain the second-level field, with the first chart being the object of the third operation; based on the second-level field and the second chart type, display the second chart in the chart component of the first table.

[0071] The third operation is performed on the currently displayed first chart. The first chart serves as the starting point for data dimension switching, using the first-level fields corresponding to the first data dimension to complete data aggregation and visualization. Based on the pre-configured order or hierarchical relationship between multiple level fields in the chart components of the first table, the second-level field corresponding to the first-level field can be automatically matched, located, and retrieved. The data display granularity indicated by the first data dimension corresponding to the first-level field is lower than that indicated by the second data dimension corresponding to the second-level field. The data granularity corresponding to the second-level field is finer, and the division dimensions are more specific, enabling further splitting and refinement of the data aggregated by the first-level field. This allows for a progressive switching display of the chart from coarse-grained to fine-grained data dimensions. After determining the second-level field, the second chart type pre-bound to the second-level field is directly called, keeping the data source as the data records of the first table, and only updating the data grouping method, statistical dimensions, and display style. Without switching chart components, reloading the page, or reconfiguring the data source, the second chart can be rendered and displayed directly within the chart component of the first table, achieving a seamless transition from the first chart to the second chart.

[0072] The technical advantage of the above solution is that it allows for progressive data analysis from coarse-grained to fine-grained directly within the chart component of the first table. There is no need to manually exit the chart component, reselect fields, or reconfigure the chart. It can automatically identify and switch to the next level of data dimension based on the hierarchical relationship of multiple configured fields. The operation path is short, the interaction is intuitive, and the operation cost of data analysis is greatly reduced.

[0073] In some cases, it can be combined with one or more of the alternatives mentioned above to display a second chart in the chart component of the first table in response to the third operation. Specifically, this may include the following steps: Obtain the data dimension pointed to by the third operation. The first chart is the operation object of the third operation, and the data dimension pointed to by the third operation corresponds to the data area pointed to by the third operation in the first chart. Based on the first-level field of the first chart, obtain the second-level field corresponding to the data dimension pointed to by the third operation. Based on the second-level field corresponding to the data dimension pointed to by the third operation and the second chart type, display the second chart in the chart component of the first table.

[0074] The third operation can be an action triggered by the currently displayed first chart, switching chart dimensions and refining data display. The third operation targets a data area within the first chart. The first chart, as the object of the third operation, is a visualization chart generated and rendered based on the data records of the first table, relying on the first data dimension corresponding to the first-level fields. It is currently displayed within the chart component of the first table. The data dimension targeted by the third operation can be a local data dimension locked based on the specific trigger position of the third operation within the first chart. The data dimension targeted by the third operation directly corresponds to the specific data area selected by the third operation within the first chart, not the global data dimension displayed by the entire first chart, thus possessing locality and specificity. In other words, the first chart as a whole displays the first data dimension corresponding to the first-level fields, which is the global data dimension, while the third operation targets a specific local data range within that data dimension on the first chart.

[0075] The second-level field can be a data field already created in the first table. It is a lower-level dimension field that has a hierarchical relationship and progressive granularity with the first-level field. The second-level field corresponds to the second data dimension and offers higher precision and finer granularity in the Xining data segmentation. It matches the data area pointed to by the third operation in the first chart, and is used to further decompose and analyze this data area. After determining the second-level field, the second chart type pre-bound to it is directly called. Data records from the first table are read synchronously, and for the data dimension pointed to by the third operation, local data is aggregated and calculated according to the statistical rules and grouping logic of the second-level field. Throughout the process, the data source remains the data records from the first table; no new, deleted, or modified data records are added. Only the statistical dimensions and display format are adjusted for a local range. There is no need to switch chart components, reload the page, or manually configure any parameters. The dynamic rendering and display of the second chart is completed directly within the chart component display area of ​​the first table, achieving a seamless switch from the first chart to the second chart.

[0076] The technical advantage of the above solution is that it achieves precise and targeted chart dimension switching. Unlike overall dimension switching, it allows for refined and progressive display of local data areas, significantly improving the focus of data analysis. Relying on pre-configured hierarchical field relationships, it automatically completes dimension matching and chart switching without the need for manual field filtering, chart reconfiguration, component switching, or page refresh, simplifying the operation process and reducing interaction complexity. Simultaneously, targeted local dimension switching avoids recalculating and loading the entire chart data, improving chart rendering response speed, ensuring data display continuity, optimizing in-depth data analysis operations, and adapting to various scenarios requiring refined data breakdown and analysis.

[0077] In some cases, it can be combined with one or more of the above-mentioned alternatives. The second chart is associated with second information, which includes at least a first-level field and a second-level field displayed in hierarchical order. The second information is displayed in the form of breadcrumb navigation. The chart processing method in this article also includes the following steps: in response to the display of the second chart in the chart component of the table of the first chart and the triggering operation of the first-level field in the breadcrumb navigation, the first chart is switched from the second chart to the first chart in the chart component of the first table.

[0078] See Figure 7The breadcrumb navigation is displayed in the following format: {N levels above} > ... > {one level above} > {selected dimension value of the previous level}, where the N levels above are all text in preset colors and are clickable. Clicking the level field corresponding to the N levels above cancels the level field switching state if the switching level field is in the first level, and the option to switch to the next level field is no longer displayed. By displaying the configured level fields of the chart component in the form of breadcrumb navigation as the first table, the drill-down level path of the current chart can be presented intuitively and clearly, quickly locating the data's position in the overall hierarchical structure. Moreover, responding to the trigger operation of the eighth level field in the breadcrumb navigation allows for a quick switch from the second chart to the first chart without having to go back level by level, simplifying the operation process, improving interaction efficiency, and realizing the linkage between hierarchical display and chart switching operation. This makes the drill-down path visible and the operation directly accessible, improving the coherence and convenience of the data analysis process.

[0079] In the above method, receiving the first operation allows configuration of multiple hierarchical fields and corresponding chart types for the chart component in the first table. This enables the sequential display of charts corresponding to different hierarchical fields based on these fields and their corresponding chart types. This allows for flexible switching between different data dimensions and chart display formats within the same chart component, eliminating the need for complex configuration operations and enabling rapid switching of data display dimensions and granularity, significantly simplifying the chart visualization configuration process. The second operation displays the first chart within the chart component. This first chart is generated based on existing data records in the first table and possesses a first data dimension and first chart type matching the first hierarchical field. It can automatically complete the visualization rendering of the target dimension data, accurately presenting the first data dimension corresponding to the first hierarchical field. The proposed solution enables rapid visualization of single data dimensions, ensuring the immediacy and relevance of data presentation. Furthermore, it responds to third operations by seamlessly switching to a second chart within the same chart component. This second chart, also generated from the existing data records of the first table, possesses a second data dimension and chart type matching the second-level fields. This allows for rapid presentation of visualization results corresponding to the second-level fields without the need to create new charts or reload the data source, achieving seamless switching between different data analysis dimensions. This solution effectively overcomes the inherent limitations of charts, such as single analytical dimensions and cumbersome dimension switching processes, improving the efficiency of online table data exploration and multidimensional data analysis, and resolving the issues of complex data display dimension switching operations and insufficient data analysis flexibility.

[0080] Figure 8A schematic diagram of a chart processing device is provided for a specific scenario. This device is applicable to scenarios where different data dimensions and different chart display formats can be flexibly switched within the same chart component of an online table. The device can be implemented in software and / or hardware, optionally through electronic devices such as mobile terminals, PCs, or servers. Figure 8 As shown, the chart processing apparatus in this article may include the following: The receiving module 810 is used to receive a first operation, which is used to configure multiple hierarchical fields and chart types corresponding to the hierarchical fields for a chart component in a first table, wherein the hierarchical fields are fields that have been created in the first table; The first display module 820 is configured to display a first chart in the chart component in response to a second operation. The first chart is created based on the data records of the first table and has a first data dimension and a first chart type corresponding to the first level field. The second display module 830 is configured to display a second chart in the chart component in response to a third operation. The second chart is created based on the data records of the first table and has a second data dimension and a second chart type corresponding to a second-level field. The first-level field is the first field in the first table, and the second-level field is the second field in the first table.

[0081] In one scenario, it can be combined with various optional schemes from one or more of the above scenarios. The multiple hierarchical fields correspond to hierarchical numbers, which are used to indicate the display level of each hierarchical field in the chart component. The chart type corresponding to the hierarchical field is used to indicate the chart display format of the corresponding display level.

[0082] In one scenario, the data for constructing the first chart can be composed of multiple sub-tables, and / or the data for constructing the second chart can be composed of multiple sub-tables; the sub-tables are data tables within the first table.

[0083] In one scenario, the receiving of the first operation can be combined with one or more of the alternative options described above, including: Receive configuration information for the hierarchical fields and chart types of the first sub-table, and receive configuration information for the hierarchical fields and chart types of the second sub-table.

[0084] In one scenario, it can be combined with one or more of the above-mentioned alternatives, wherein the first chart type and the second chart type are different chart types.

[0085] In one scenario, the device may be combined with one or more of the alternative solutions described above, and further includes: In response to the first operation including a first editing operation on the hierarchical field configuration control, the value of the hierarchical field is configured for the chart component in the first table; In response to the first operation, which includes a second editing operation on the chart type configuration control associated with the hierarchical field, the chart type corresponding to the hierarchical field is configured for the chart component in the first table.

[0086] In one scenario, the device can be combined with one or more of the above-mentioned alternatives, wherein the first table is simultaneously associated with a first sub-table and a second sub-table, and the first sub-table and the second sub-table are respectively associated with a set of multiple hierarchical fields configured in the chart component of the first table and the chart type corresponding to the hierarchical fields; the device further includes: In response to a third editing operation on multiple hierarchical fields associated with the first sub-table, the multiple hierarchical fields associated with the second sub-table are adjusted according to the editing result of the third editing operation; The third editing operation includes at least one of the following: adding at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table; deleting at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table; modifying the value of at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table; adjusting the chart type corresponding to at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table; and adjusting the hierarchical order of at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table.

[0087] In one scenario, a second chart can be displayed in the chart component by combining it with one or more of the alternative options described above, including: Based on the first-level field of the first chart, the second-level field is obtained, and the first chart is the object of the third operation; The second chart is displayed in the chart component based on the second level field and the second chart type.

[0088] In one scenario, combining with one or more of the alternatives described above, the display of a second chart in the chart component in response to the third operation includes: Obtain the data dimension pointed to by the third operation, where the first chart is the operation object of the third operation, and the data dimension corresponds to the data area pointed to by the third operation in the first chart; Based on the first-level field of the first chart, obtain the second-level field corresponding to the data dimension; The second chart is displayed in the chart component based on the second-level field corresponding to the data dimension and the second chart type.

[0089] In the above method, receiving the first operation allows configuration of multiple hierarchical fields and corresponding chart types for the chart component in the first table. This enables the sequential display of charts corresponding to different hierarchical fields based on these fields and their corresponding chart types. This allows for flexible switching between different data dimensions and chart display formats within the same chart component, eliminating the need for complex configuration operations and enabling rapid switching of data display dimensions and granularity, significantly simplifying the chart visualization configuration process. The second operation displays the first chart within the chart component. This first chart is generated based on existing data records in the first table and possesses a first data dimension and first chart type matching the first hierarchical field. It can automatically complete the visualization rendering of the target dimension data, accurately presenting the first data dimension corresponding to the first hierarchical field. The proposed solution enables rapid visualization of single data dimensions, ensuring the immediacy and relevance of data presentation. Furthermore, it responds to third operations by seamlessly switching to a second chart within the same chart component. This second chart, also generated from the existing data records of the first table, possesses a second data dimension and chart type matching the second-level fields. This allows for rapid presentation of visualization results corresponding to the second-level fields without the need to create new charts or reload the data source, achieving seamless switching between different data analysis dimensions. This solution effectively overcomes the inherent limitations of charts, such as single analytical dimensions and cumbersome dimension switching processes, improving the efficiency of online table data exploration and multidimensional data analysis, and resolving the issues of complex data display dimension switching operations and insufficient data analysis flexibility.

[0090] The above-described chart processing apparatus can execute the chart processing method provided in any embodiment of this document, and has the corresponding functional modules and beneficial effects for executing the chart processing method.

[0091] It is worth noting that the various units and modules included in the above-mentioned interactive device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments in this article.

[0092] The following is for reference. Figure 9This document illustrates a structural diagram of an electronic device (e.g., a terminal device or server) 900 suitable for implementing the aforementioned graph processing method. The terminal device referred to herein may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 9 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments described herein.

[0093] like Figure 9 As shown, electronic device 900 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 901, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 902 or a program loaded from storage device 908 into random access memory (RAM) 903. RAM 903 also stores various programs and data required for the operation of electronic device 900. Processing device 901, ROM 902, and RAM 903 are interconnected via bus 904. Input / output (I / O) interface 905 is also connected to bus 904.

[0094] Typically, the following devices can be connected to I / O interface 905: input devices 906 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 907 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 908 including, for example, magnetic tapes, hard disks, etc.; and communication devices 909. Communication device 909 allows electronic device 900 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 9 An electronic device 900 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0095] In particular, according to embodiments of this document, the processes described in the above-referenced flowcharts can be implemented as computer software programs. For example, the technical solutions of this document include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the graph processing method shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network via a communication device 909, or installed from a storage device 908, or installed from a ROM 902. When the computer program is executed by the processing device 901, it performs the functions defined in the graph processing method of the embodiments of this document.

[0096] The names of messages or information exchanged between multiple devices in this document are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0097] The electronic device provided in this embodiment and the chart processing method provided in the above technical solutions belong to the same inventive concept. Technical details not described in detail in this document can be found in the above embodiments, and this embodiment has the same beneficial effects as the above embodiments.

[0098] This article provides a computer storage medium on which a computer program is stored, which, when executed by a processor, implements the graph processing method provided in the above embodiments.

[0099] It should be noted that the computer-readable medium described above can be a computer-readable signal medium, a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this document, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0100] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0101] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0102] The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: receive a first operation, the first operation being configured to configure multiple hierarchical fields and chart types corresponding to the hierarchical fields for a chart component in a first table, the hierarchical fields being fields already created in the first table; in response to a second operation, display a first chart in the chart component, the first chart being created based on data records of the first table and having a first data dimension and a first chart type corresponding to the first hierarchical field; and in response to a third operation, display a second chart in the chart component, the second chart being created based on data records of the first table and having a second data dimension and a second chart type corresponding to a second hierarchical field, the first hierarchical field being a first field in the first table and the second hierarchical field being a second field in the first table.

[0103] Computer program code for performing the operations described herein may be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0104] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this document. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0105] The modules or units described herein can be implemented in software or hardware. The names of modules or units do not necessarily constitute a limitation on the module or unit itself.

[0106] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.

[0107] In the context of this document, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0108] The above description is merely a preferred embodiment and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure herein is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed herein that have similar functions.

[0109] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of this document. Certain features described in the context of individual implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented individually or in any suitable sub-combination in multiple implementations.

[0110] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A chart processing method, the method comprising: Receive a first operation, the first operation being configured to configure multiple hierarchical fields and chart types corresponding to the hierarchical fields for a chart component in a first table, wherein the hierarchical fields are fields already created in the first table; In response to the second operation, a first chart is displayed in the chart component. The first chart is created based on the data records of the first table and has a first data dimension and a first chart type corresponding to the first level field. In response to the third operation, a second chart is displayed in the chart component. The second chart is created based on the data records of the first table and has a second data dimension and a second chart type corresponding to the second-level field. The first-level field is the first field in the first table, and the second-level field is the second field in the first table.

2. The method according to claim 1, wherein the plurality of hierarchical fields correspond to hierarchical numbers, the hierarchical numbers are used to indicate the display level of each hierarchical field in the chart component; the chart type corresponding to the hierarchical field is used to indicate the chart display format of the corresponding display level.

3. The method according to claim 1, wherein the data used to construct the first chart belongs to multiple sub-tables, and / or the data used to construct the second chart belongs to multiple sub-tables; the sub-tables are data tables in the first table.

4. The method according to claim 3, wherein receiving the first operation includes: Receive configuration information for the hierarchical fields and chart types of the first sub-table, and receive configuration information for the hierarchical fields and chart types of the second sub-table.

5. The method according to claim 1, wherein the first chart type and the second chart type are different chart types.

6. The method according to claim 1, further comprising: In response to the first operation including a first editing operation on the hierarchical field configuration control, the value of the hierarchical field is configured for the chart component in the first table; In response to the first operation, which includes a second editing operation on the chart type configuration control associated with the hierarchical field, the chart type corresponding to the hierarchical field is configured for the chart component in the first table.

7. The method according to claim 3, wherein the first table is simultaneously associated with a first sub-table and a second sub-table, and the first sub-table and the second sub-table are respectively associated with a set of multiple hierarchical fields configured in the chart component of the first table and a chart type corresponding to the hierarchical fields; the method further includes: In response to a third editing operation on multiple hierarchical fields associated with the first sub-table, the multiple hierarchical fields associated with the second sub-table are adjusted according to the editing result of the third editing operation; The third editing operation includes at least one of the following: adding at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table; deleting at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table; modifying the value of at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table; adjusting the chart type corresponding to at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table; and adjusting the hierarchical order of at least one hierarchical field among the multiple hierarchical fields associated with the first sub-table.

8. The method of claim 1, wherein displaying the second chart in the chart component in response to the third operation comprises: Based on the first-level field of the first chart, the second-level field is obtained, and the first chart is the object of the third operation; The second chart is displayed in the chart component based on the second level field and the second chart type.

9. The method of claim 1, wherein displaying the second chart in the chart component in response to the third operation comprises: Obtain the data dimension pointed to by the third operation, where the first chart is the operation object of the third operation, and the data dimension corresponds to the data area pointed to by the third operation in the first chart; Based on the first-level field of the first chart, obtain the second-level field corresponding to the data dimension; The second chart is displayed in the chart component based on the second-level field corresponding to the data dimension and the second chart type.

10. A chart processing apparatus, the apparatus comprising: A receiving module is used to receive a first operation, the first operation being used to configure multiple hierarchical fields and chart types corresponding to the hierarchical fields for a chart component in a first table, wherein the hierarchical fields are fields that have been created in the first table; A first display module is configured to respond to a second operation by displaying a first chart in the chart component. The first chart is created based on the data records of the first table and has a first data dimension and a first chart type corresponding to the first level field. The second display module is used to display a second chart in the chart component in response to a third operation. The second chart is created based on the data records of the first table and has a second data dimension and a second chart type corresponding to a second-level field. The first-level field is the first field in the first table, and the second-level field is the second field in the first table.

11. An electronic device, the electronic device comprising: At least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-9.

12. A computer-readable storage medium storing computer instructions that, when executed by a processor, implement the method of any one of claims 1-9.

13. A computer program product comprising a computer program that, when executed by a processor, implements the method as described in any one of claims 1-9.

Images