A method, apparatus, device, and storage medium for troubleshooting column naming errors.

By obtaining the sales system summary table and determining the priority of pre-selected column names based on the differences between newly added data rows and historical data rows, and marking them with colors, the communication barrier between the sales system and the business activation system is resolved, the efficiency of identifying incorrect column names is improved, and the processing difficulty and time consumption are reduced.

CN117875679BActive Publication Date: 2026-11-10CHINA UNITED NETWORK COMM GRP CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202410057494.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-01-15
Publication Date
2026-11-10
Estimated Expiration
2044-01-15

AI Technical Summary

Technical Problem

There is a communication barrier between the sales system and the business activation system, which makes it impossible to activate the business normally when the customer type and product attribute are entered incorrectly. Existing technical means are inefficient and rely on personal experience, and cannot effectively identify potentially incorrect column names.

Method used

By obtaining the sales system summary table, the priority of the pre-selected column names is determined based on the difference between newly added data rows and historical data rows. The priority is then marked in the sales system data, and a color scheme is used to indicate the probability of errors.

Benefits of technology

It breaks down communication barriers between the sales system and the business activation system, improves the efficiency of identifying incorrect column names, reduces the processing difficulty for account managers or front desk data entry personnel, and saves time in problem handling.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117875679B_ABST
    Figure CN117875679B_ABST
Patent Text Reader

Abstract

This application provides a method, apparatus, device, and storage medium for troubleshooting column name errors, relating to the field of electronic digital data processing technology. The method includes: when the activation of a new user's service fails, obtaining a sales system summary table; determining at least one distinguishing data row from multiple historical data rows based on the newly added data row; obtaining the priority of each pre-selected column name based on the number of distinguishing data rows corresponding to each pre-selected column name; and marking the priority of the sales system data corresponding to each pre-selected column name in the sales system data corresponding to the newly added data row. This method solves the problem of how to determine potentially erroneous column names when there are communication barriers between the sales system and the service activation system.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of electronic digital data processing technology, and in particular to a method, apparatus, device and storage medium for troubleshooting column naming errors. Background Technology

[0002] In many companies, account managers or front-line data entry personnel typically use the sales system to enter customer types and product attributes, which are then sent to the business activation system. Incorrect customer type or product attribute entries can lead to inconsistencies with the pre-defined logic of the back-end activation system, preventing the business from being activated properly.

[0003] Account managers or front desk data entry staff often contact the staff in the business activation system, but because the staff in the business activation system are unfamiliar with the sales system, they are unable to provide guidance, resulting in ineffective or inefficient communication. Account managers or front desk data entry staff typically modify some column names for customer types or product attributes based on their past experience, repeatedly entering the data into the sales system, and then contacting the business activation system staff for verification. While this technical approach can solve some problems, it is inefficient and degrades the customer experience.

[0004] Summarizing obstacle handling experience using an obstacle support knowledge base can solve some problems. However, due to untimely updates to the obstacle support knowledge base or rapid system updates, account managers or front desk data entry personnel may lack sufficient obstacle handling experience, resulting in poor support effectiveness of the obstacle support knowledge base.

[0005] Given the communication barriers between the sales system and the business activation system, determining potentially incorrect column names is a problem that this invention urgently needs to solve. Summary of the Invention

[0006] This application provides a method, apparatus, device, and storage medium for troubleshooting column names errors, which addresses the problem of determining potentially erroneous column names when communication barriers exist between the sales system and the business activation system.

[0007] Firstly, this application provides a method for troubleshooting column naming errors, the method comprising:

[0008] When the service activation of a new user fails, the sales system summary table is retrieved. The sales system summary table includes multiple rows of historical data and one row of new data. Each historical user corresponds to one historical data row, and each new user corresponds to one new data row. Each historical user refers to a user whose service activation was successful.

[0009] Based on the newly added data row, at least one distinguishing data row is determined from multiple historical data rows, wherein the cell data of the first number of pre-selected column names in each distinguishing data row is different from the corresponding cell data in the newly added data row;

[0010] The priority of each preselected column name is obtained based on the number of rows of distinguishing data corresponding to each preselected column name. The priority is used to indicate the probability of error in the cell data of each preselected column name in the newly added data row.

[0011] In the sales system data corresponding to the newly added data rows, mark the priority of the sales system data corresponding to each pre-selected column name.

[0012] In one possible design, the priorities include: a first level, a second level, a third level, and a fourth level that are positively correlated with the error probability of reverse sorting;

[0013] The priority of each preselected column name is determined based on the number of rows in the distinguishing data corresponding to each preselected column name, including:

[0014] Reverse sort multiple rows to obtain the first row number and the second row number, where the first row number refers to the row number that is first in the reverse sort result, and the second row number refers to the row number that is second in the reverse sort result;

[0015] Based on the second row number, the third row number is obtained, where the third row number is equal to the product of the second row number and the preset second quantity;

[0016] When the number of rows in the first row is greater than the number of rows in the third row, the first level or the third level shall be used as the priority of the pre-selected column name corresponding to the first row number, and the second level or the fourth level shall be used as the priority of the pre-selected column name corresponding to the fourth row number. Here, the fourth row number refers to any one of the multiple row numbers other than the first row number.

[0017] When the number of rows in the first row is no greater than the number of rows in the third row, the second or fourth level will be used as the priority for the pre-selected column names corresponding to each row number.

[0018] In one possible design, when the first quantity equals one, the first or third level is used as the priority for the pre-selected column name corresponding to the first row number, and the second or fourth level is used as the priority for the pre-selected column name corresponding to the fourth row number, including:

[0019] The first level is used as the priority for the pre-selected column name corresponding to the first row number, and the second level is used as the priority for the pre-selected column name corresponding to the fourth row number;

[0020] Prioritize the second or fourth level as the pre-selected column name for each row number, including:

[0021] The second level is used as the priority for the pre-selected column names corresponding to each row number.

[0022] In one possible design, when the first quantity equals two, the first or third level is prioritized as the priority of the pre-selected column name corresponding to the first row number, and the second or fourth level is prioritized as the priority of the pre-selected column name corresponding to the fourth row number, including:

[0023] The third level is used as the priority for the pre-selected column name corresponding to the first row number, and the fourth level is used as the priority for the pre-selected column name corresponding to the fourth row number;

[0024] Prioritize the second or fourth level as the pre-selected column name for each row number, including:

[0025] The fourth level is used as the priority for the pre-selected column name corresponding to each row number.

[0026] In one possible design, a historical error summary table is pre-stored. The historical error summary table includes multiple rows of historical error data. Each row of historical error data includes a historical error column name and a historical pre-selected column name. The historical error column name is obtained from the business activation system.

[0027] Before marking the priority of each pre-selected column name in the sales system data corresponding to the newly added data row, the method also includes:

[0028] Obtain the error column names from the service activation system;

[0029] Based on the error column name, determine the target error data row from multiple historical error data rows, obtain the historical pre-selected column name of the target error data row, and the historical error count of the historical pre-selected column name of the target error data row, wherein the error column name is the same as the historical error column name of the target error data row;

[0030] Determine the target preselected column name from a variety of preselected column names, wherein the target preselected column name is the same as the historical preselected column name of the target error data row;

[0031] When the number of historical error reports exceeds the preset third number, the first level will be used as the priority for the target pre-selected column name;

[0032] If the number of historical error reports is no greater than the third number, and the priority of the target pre-selected column name is not the first level, the second level will be used as the priority of the target pre-selected column name.

[0033] In one possible design, the sales system pre-stores a customer type table and a product attribute table. The customer type table includes a user identifier column name, and the product attribute table includes a product type column name.

[0034] Obtain the sales system summary table, including:

[0035] Based on the relationship between the user identifier column name and the product type column name, the customer type table and the product attribute table are linked to obtain the sales system summary table.

[0036] In one possible design, the priority of the sales system data corresponding to each pre-selected column name is marked in the sales system data corresponding to the newly added data row, including:

[0037] Based on the mapping relationship between priority and the set of annotation colors, the sales system data corresponding to each priority is annotated in the sales system data corresponding to the newly added data row using the set of annotation colors.

[0038] Secondly, this application provides a column naming error troubleshooting device, the device comprising:

[0039] The acquisition module is used to retrieve the sales system summary table when the service activation of a new user fails. The sales system summary table includes multiple rows of historical data and one row of new data. Each historical user corresponds to one historical data row, and each new user corresponds to one new data row. Each historical user refers to a user whose service activation was successful.

[0040] The pre-selected column name module is used to determine at least one distinguishable data row from multiple historical data rows based on the new data row. In each distinguishable data row, the cell data of the first number of pre-selected column names is different from the corresponding cell data in the new data row.

[0041] The priority confirmation module is used to determine the priority of each preselected column name based on the number of rows of distinguishing data corresponding to each preselected column name. The priority is used to indicate the probability of error in the cell data of each preselected column name in the newly added data row.

[0042] The annotation module is used to annotate the priority of each pre-selected column name in the sales system data corresponding to the newly added data row.

[0043] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0044] The memory stores instructions that the computer executes;

[0045] When a processor executes computer execution instructions stored in memory, it provides a method for troubleshooting column names that implements the contents of the first aspect of the invention.

[0046] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement a column name error detection method according to the first aspect of the invention.

[0047] Fifthly, this application provides a computer program product, including a computer program, which, when executed by a processor, is used to implement a method for troubleshooting column names as described in the first aspect of the invention.

[0048] This application provides a method, apparatus, device, and storage medium for troubleshooting column name errors. When the activation of a new user's service fails, the method involves: obtaining a sales system summary table; determining at least one distinguishing data row from multiple historical data rows based on the newly added data row; obtaining the priority of each pre-selected column name based on the number of distinguishing data rows corresponding to each pre-selected column name; and marking the priority of the sales system data corresponding to each pre-selected column name in the sales system data corresponding to the newly added data row. This achieves the following technical effects: by determining at least one distinguishing data row from multiple historical data rows based on the newly added data row, and obtaining the priority of each pre-selected column name based on the number of distinguishing data rows corresponding to each pre-selected column name, the problem of how to determine potentially incorrect column names when there are communication barriers between the sales system and the service activation system is addressed; by obtaining the sales system summary table when the activation of a new user's service fails, the problem of how to bypass the communication barriers between the sales system and the service activation system is solved. Attached Figure Description

[0049] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0050] Figure 1 A flowchart illustrating a column naming error troubleshooting method provided in this application embodiment. Figure 1 ;

[0051] Figure 2 A flowchart illustrating a column naming error troubleshooting method provided in this application embodiment. Figure 2 ;

[0052] Figure 3 A schematic diagram of a column name error checking device provided in an embodiment of this application;

[0053] Figure 4 This is a schematic diagram of the structure of the electronic device hardware provided in the embodiments of this application.

[0054] Figure label:

[0055] 100 - Column name error troubleshooting device; 110 - Acquisition module; 120 - Pre-selected column name module; 130 - Priority confirmation module; 140 - Labeling module;

[0056] 200 - Electronic device; 210 - Processor; 220 - Memory; 230 - Communication component; 240 - Bus. Detailed Implementation

[0057] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0058] In the embodiments of this application, the terms "first" and "second" are used to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, nor do they necessarily imply difference. It should be noted that in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner. In the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more.

[0059] It should be noted that the phrase "at...time" in the embodiments of this application can refer to the instant at which a certain situation occurs, or to a period of time after the occurrence of a certain situation; the embodiments of this application do not specifically limit this. Furthermore, the column name error troubleshooting method provided in the embodiments of this application is merely an example; a column name error troubleshooting method may include more or fewer elements.

[0060] To facilitate a clear description of the technical solutions in the embodiments of this application, some terms and technologies involved in the embodiments of this application will be briefly introduced below:

[0061] Sales system: Used for entering customer types and product attributes. The sales system sends the column names to the business activation system. When the customer type and product attribute are entered incorrectly, it may cause a discrepancy with the pre-set logic of the backend activation system, resulting in the business failing to be activated normally.

[0062] Pre-selected column names: These refer to the column names that the sales system might enter incorrectly when the service activation system reports an error in the column names of newly added users.

[0063] Currently, due to the complex and iterative accumulation of business logic between the sales system and the back-end activation system, a difficult-to-overcome technical barrier exists between the two systems—the column names in the front-end and back-end databases cannot be correlated, thus creating a logical correspondence to handle problems. To circumvent this technical barrier, three common approaches are used to solve the problem:

[0064] 1. The account manager or front desk data entry staff contacted the staff of the business activation system, who only provided guidance based on their own experience in supporting the business; 2. The account manager or front desk data entry staff would usually modify some column names for customer types or product attributes based on their past experience, repeatedly enter the data into the sales system, and then contact the staff of the business activation system for verification; 3. Summarizing obstacle handling experience using the obstacle support knowledge base can solve some problems.

[0065] However, when account managers or front desk data entry personnel contact the staff of the business activation system, the staff there only provide guidance based on their own business experience. This guidance is often mixed with specialized knowledge, and because the staff of the business activation system are unfamiliar with the sales system, they cannot offer truly effective or inefficient communication. Even when they do offer guidance, it is often not very helpful. Account managers or front desk data entry personnel typically modify some column names for customer types or product attributes based on their past experience, repeatedly entering the data into the sales system, and then contacting the staff of the business activation system for verification. This technical approach can solve some problems, but relying on it is inefficient and degrades the customer's actual experience.

[0066] Summarizing obstacle handling experience using an obstacle support knowledge base can solve some problems. However, due to untimely updates to the obstacle support knowledge base or rapid system updates, account managers or front desk data entry personnel may lack sufficient obstacle handling experience, resulting in poor support effectiveness of the obstacle support knowledge base.

[0067] Given the communication barriers between the sales system and the business activation system, determining potentially incorrect column names is a problem that this invention urgently needs to solve.

[0068] Based on this, embodiments of this application provide a method, apparatus, device, and storage medium for troubleshooting column naming errors, which can be used in the field of electronic digital data processing technology and aims to solve the above-mentioned technical problems of the prior art.

[0069] Example 1

[0070] Figure 1 A flowchart illustrating a column naming error troubleshooting method provided in this application embodiment. Figure 1 .like Figure 1 As shown, the method includes:

[0071] S101. When the activation of services for a new user fails, obtain the sales system summary table;

[0072] Specifically, the sales system summary table includes multiple rows of historical data and one row of new data. Each historical user corresponds to one historical data row, and each new user corresponds to one new data row. Each historical user refers to a user who has successfully activated the service.

[0073] When a new user's service activation fails, i.e. when the service activation system reports an error, retrieve the sales system summary table.

[0074] S102. Based on the newly added data row, determine at least one distinguishing data row from multiple historical data rows;

[0075] Specifically, the cell data of the first number of pre-selected column names in each distinguishing data row is different from the corresponding cell data in the newly added data row;

[0076] Compare newly added data rows with historical data rows, and filter out the first number of historical data rows with different column names in the pre-selected column names as the distinguishing data rows. The pre-selected column names are the column names that may have been entered incorrectly.

[0077] S103. Based on the number of rows of distinguishing data corresponding to each pre-selected column name, obtain the priority of each pre-selected column name;

[0078] Specifically, priority is used to indicate the probability of error in the cell data of each preselected column name in the new data row; the priority of each preselected column name is obtained based on the number of distinct data rows filtered out for each preselected column name in the new data row.

[0079] S104. In the sales system data corresponding to the newly added data row, mark the priority of the sales system data corresponding to each pre-selected column name;

[0080] Specifically, in the sales system data corresponding to the newly added data row, the priority of each column name that may be entered incorrectly is marked to indicate the probability of that column name being incorrect.

[0081] This application provides a method for troubleshooting column name errors. When the activation of a new user's service fails, the method retrieves a summary table from the sales system. Based on the newly added data row, it identifies at least one distinguishing data row from multiple historical data rows. The priority of each pre-selected column name is determined based on the number of distinguishing data rows corresponding to each pre-selected column name. The priority of the sales system data corresponding to each pre-selected column name is then marked in the sales system data corresponding to the newly added data row. This achieves the following technical effects: by identifying at least one distinguishing data row from multiple historical data rows based on the newly added data row, and by determining the priority of each pre-selected column name based on the number of distinguishing data rows corresponding to each pre-selected column name, the method solves the problem of determining potentially incorrect column names when there are communication barriers between the sales system and the service activation system. Furthermore, by retrieving the summary table from the sales system when the activation of a new user's service fails, the method solves the problem of bypassing the communication barriers between the sales system and the service activation system.

[0082] Example 2

[0083] Figure 2 A flowchart illustrating a column naming error troubleshooting method provided in this application embodiment. Figure 2 This embodiment is in Figure 1 Based on the implementation examples, the method for troubleshooting column naming errors is described in detail. For example... Figure 2 As shown, the method includes:

[0084] S201. Based on the relationship between the user identifier column name and the product type column name, link the customer type table and the product attribute table to obtain the sales system summary table.

[0085] Specifically, when the activation of a new user's service fails, the sales system has a pre-stored customer type table and a product attribute table. The customer type table includes a user identifier column name, and the product attribute table includes a product type column name.

[0086] Each customer is assigned a unique user identifier column named customerID. The sales system database has 'a' columns related to customer type and product attributes, which are linked based on customerID to generate a sales system summary table with columns named N1, N2...Na. The business activation system has 'b' columns related to production, which are linked based on customerID to generate a business activation system summary table with columns named M1, M2...Mb.

[0087] In one example, Table 1 is a customer type table provided in an embodiment of this application, showing the three column names and specific data of the customer type table.

[0088] Table 1:

[0089]

[0090] Table 2 is a product attribute table provided in the embodiments of this application, showing the three column names and specific data of the product attribute table.

[0091] Table 2:

[0092]

[0093] Table 3 is a customer and product attribute association table provided in the embodiments of this application, showing the association between the user identifier column name and the product type column name.

[0094] Table 3:

[0095]

[0096] Table 4 is a sales system summary table provided in the embodiments of this application, showing the six column names and specific data of the sales system summary table. As shown in Table 4, the sales system summary table is obtained by associating the customer type table and the product attribute table according to the relationship between the user identifier column name and the product type column name.

[0097] Table 4:

[0098]

[0099] Table 5 is a summary table of the business activation system provided in the embodiments of this application. It shows the five column names and specific data of the summary table of the business activation system when the business is activated normally. As shown in Table 5, the sales system sends the column names to the business activation system, activates the business normally according to the preset settings of the backend activation system, and generates the summary table of the business activation system.

[0100] Table 5:

[0101]

[0102] Table 6 is a summary table of the sales system for customer C provided in this application embodiment. As shown in Table 6, there is a customer C. After merging the three sales system tables (customer type table, product attribute table, and customer and product attribute association table), the information entered is as follows:

[0103] Table 6:

[0104]

[0105] Table 7 is a summary table of the customer C service activation system provided in the embodiments of this application. As shown in Table 7, if the service activation fails, the service activation system will show an error in the PON_tpye column.

[0106] Table 7:

[0107]

[0108] When a customer with customerID C attempts to activate the service, an error occurs in Mx (Mx is any column related to production, i.e., any column among M1, M2...Mb), causing the service activation to fail.

[0109] It should be noted that the table above only shows one possible scenario and does not mean that the table only contains the above column names and specific data.

[0110] S202. Based on the newly added data row, determine at least one distinguishing data row from multiple historical data rows;

[0111] Specifically, a search is performed in multiple rows of historical data. The historical data of columns N1, N2...Na of customers who have successfully activated their accounts are compared with the column names of columns N1, N2...Na of customer C with customerID 4. At least one distinguishing data row is determined from the multiple rows of historical data. The data of the first number of column names in the distinguishing data row is different from that of customer C with customerID 4.

[0112] S203. When the first quantity is equal to one, and the number of rows in the first row is greater than the number of rows in the third row, the first level is used as the priority of the pre-selected column name corresponding to the number of rows in the first row, and the second level is used as the priority of the pre-selected column name corresponding to the number of rows in the fourth row; when the number of rows in the first row is not greater than the number of rows in the third row, the second level is used as the priority of the pre-selected column name corresponding to each row number.

[0113] Specifically, the first, second, third, and fourth levels are positively correlated with the error probability of reverse sorting; multiple rows are reverse sorted to obtain the first and second row numbers, where the first row number refers to the row that is first in the reverse sorting result, and the second row number refers to the row that is second in the reverse sorting result; based on the second row number, the third row number is obtained, where the third row number is equal to the product of the second row number and a preset second quantity; the fourth row number refers to any one of the multiple row numbers except the first row number; the error probability of the pre-selected column names in the first, second, third, and fourth levels decreases in that order.

[0114] If there is a record in the historical data where only one column differs from customer C with customerID 4, this column is denoted as N1. This process continues, generating a column name table of N1, N2…Nc (column names can be repeated). The frequency of each column name (N1, N2…Nc) is calculated. If the frequency of the most frequent column name is more than three times that of the second most frequent column name, then the most frequent column name is assigned the first priority, and the other column names are assigned the second priority. If the above conditions are not met, all column names are assigned the second priority.

[0115] S204. When the first number is equal to two, and the number of rows in the first row is greater than the number of rows in the third row, the third level is given priority as the priority of the pre-selected column name corresponding to the number of rows in the first row, and the fourth level is given priority as the priority of the pre-selected column name corresponding to the number of rows in the fourth row; when the number of rows in the first row is not greater than the number of rows in the third row, the fourth level is given priority as the priority of the pre-selected column name corresponding to each row number.

[0116] Specifically, if there is a record in the historical data where only two columns differ from customer C with customerID 4, this record is denoted as N1. This process continues, generating a list of column names N1, N2…Nd (column names can be repeated). The frequency of each column name (N1, N2…Nd) is calculated. If the frequency of the most frequent column name is more than three times that of the second most frequent column name, then the most frequent column name is assigned the third priority, and the other column names are assigned the fourth priority. If the above conditions are not met, all column names are assigned the fourth priority.

[0117] In one example, the service activation system encountered an error in the PON_type column. A line-by-line comparison between the customer C sales system summary table and the sales system summary table yielded the following results:

[0118] 1. The only difference between this customer and the one with CustomerID 1 is the name of one column: Access_type.

[0119] 2. There are 4 different column names for the customer with CustomerID 2;

[0120] 3. There are 4 different column names for the data of the customer with CustomerID 3;

[0121] As shown above, when the first quantity is equal to one or two, that is, when the data of one or two column names are different, the occurrence count of each column name is calculated. That is, the occurrence count of Access_type is 1, there is no column name with the second highest occurrence count, and the priority of Access_type is the first level.

[0122] S205. Obtain the error column name from the business activation system; based on the error column name, determine the target error data row from multiple historical error data rows, obtain the historical pre-selected column name of the target error data row, and the historical error count of the historical pre-selected column name of the target error data row;

[0123] Specifically, a historical error summary table is pre-stored. The historical error summary table includes multiple rows of historical error data. Each row of historical error data includes one type of historical error column name and one type of historical pre-selected column name. The historical error column name is obtained from the business activation system. The error column name is the same as the historical error column name of the target error data row.

[0124] The historical error summary table records the column names of historical errors and the column names of data entry errors finally confirmed by technical personnel. The historical error summary table contains at least two columns: historical error column names (i.e., the column names of errors reported in the business activation system) and historical pre-selected column names (i.e., the column names of data entry errors reported in the sales system). The number of historical errors can be determined based on the number of rows of the target error data, or it can be recorded in the historical error summary table as a separate column. Searching for column name Mx in the "Historical Error Column Names" returns the found "Historical Pre-selected Column Names" and "Historical Error Count".

[0125] S206. Determine the target pre-selected column name from multiple pre-selected column names; when the number of historical error reports is greater than the preset third number, use the first level as the priority of the target pre-selected column name; when the number of historical error reports is not greater than the third number, and the priority of the target pre-selected column name is not the first level, use the second level as the priority of the target pre-selected column name.

[0126] Specifically, the target pre-selected column name is the same as the historical pre-selected column name of the target error data row; the found "historical pre-selected column name" is returned as the target pre-selected column name. If the number of historical errors of the target pre-selected column name is greater than the preset third number, the priority of the column name is adjusted to the first level; if it is not greater than the third number and the priority of the target pre-selected column name is not the first level, the priority is adjusted to the second level.

[0127] In one example, the system searches the historical error summary table records based on the error column name PON_type. A record is found in the historical records, and the corresponding historical preselected column name parameter is Access_type, the number of historical errors is 1, and the third quantity can be preset to 5. The number of historical errors is less than 5, but since the priority of Access_type is the first level, there is no need to adjust the priority of Access_type.

[0128] S207. Based on the mapping relationship between priority and the set of annotation colors, in the sales system data corresponding to the newly added data row, the sales system data corresponding to each priority is annotated by the set of annotation colors respectively;

[0129] Specifically, the priority of column names can be indicated by a four-level color coding system.

[0130] This application provides a method for troubleshooting column name errors. When the activation of a new user's business fails, the method retrieves a summary table of the sales system; based on the new data row, it determines at least one distinguishing data row from multiple historical data rows; based on the number of distinguishing data rows corresponding to each pre-selected column name, it obtains the priority of each pre-selected column name; and in the sales system data corresponding to the new data row, it marks the priority of the sales system data corresponding to each pre-selected column name. The following technical effects were achieved: By identifying at least one distinguishing data row from multiple historical data rows based on newly added data rows, and determining the priority of each pre-selected column name based on the number of distinguishing data rows corresponding to each pre-selected column name, the problem of how to determine potentially incorrect column names when there are communication barriers between the sales system and the business activation system was solved; By obtaining the sales system summary table when the business activation of a new user fails, the problem of how to bypass the communication barrier between the sales system and the business activation system was solved; When customer type and product attribute are entered incorrectly, the business activation system can send the parameters to the sales system. The sales system can then judge based on the above logic, determining that the higher the priority of the column name in the sales system, the greater the likelihood that the problem point is there. This is then distinguished by color on the sales system interface. This method bypasses the technical barriers between the sales system and the business activation system, does not rely on personal experience, reduces the difficulty of problem solving for account managers or front-line data entry personnel, and saves time in problem handling, thereby improving efficiency.

[0131] In this embodiment of the invention, electronic devices or main control devices can be divided into functional modules according to the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional module. It should be noted that the module division in this embodiment of the invention is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0132] Figure 3 This is a schematic diagram of a column name error troubleshooting device provided in an embodiment of this application. Figure 3 As shown, the column name error troubleshooting device 100 includes: an acquisition module 110, a pre-selected column name module 120, a priority confirmation module 130, and a labeling module 140;

[0133] The acquisition module 110 is used to acquire the sales system summary table when the business activation of a new user fails. The sales system summary table includes multiple historical data rows and one new data row. Each historical user corresponds to one historical data row, and the new user corresponds to one new data row. Each historical user refers to a user whose business activation was successful.

[0134] The pre-selected column name module 120 is used to determine at least one distinguishable data row from multiple historical data rows based on the newly added data row, wherein the cell data of the first number of pre-selected column names in each distinguishable data row is different from the corresponding cell data in the newly added data row.

[0135] The priority confirmation module 130 is used to obtain the priority of each preselected column name based on the number of rows of the distinguishing data rows corresponding to each preselected column name. The priority is used to indicate the probability of error in the cell data of each preselected column name in the newly added data row.

[0136] The annotation module 140 is used to annotate the priority of each pre-selected column name in the sales system data corresponding to the newly added data row.

[0137] In one possible design, the priorities include: a first level, a second level, a third level, and a fourth level that are positively correlated with the error probability of reverse sorting;

[0138] Priority confirmation module 130 includes: row number module and priority assignment module;

[0139] The row count module is used to reverse sort multiple row counts to obtain the first row count and the second row count. The first row count refers to the row count that is first in the reverse sort result, and the second row count refers to the row count that is second in the reverse sort result. Based on the second row count, the third row count is obtained, where the third row count is equal to the product of the second row count and a preset second quantity.

[0140] The priority assignment module is used to assign either the first or third priority level to the pre-selected column name corresponding to the first row number when the first row number is greater than the third row number, and to assign either the second or fourth priority level to the pre-selected column name corresponding to the fourth row number. Here, the fourth row number refers to any one of the multiple row numbers other than the first row number. When the first row number is not greater than the third row number, the second or fourth priority level is assigned to the pre-selected column name corresponding to each row number.

[0141] In one possible design, when the first quantity equals one;

[0142] The priority confirmation module 130 is used to set the first level as the priority of the pre-selected column name corresponding to the first row number, and set the second level as the priority of the pre-selected column name corresponding to the fourth row number; and set the second level as the priority of the pre-selected column name corresponding to each row number.

[0143] In one possible design, when the first quantity equals two;

[0144] The priority confirmation module 130 is used to prioritize the third level as the priority of the pre-selected column name corresponding to the first row number, and to prioritize the fourth level as the priority of the pre-selected column name corresponding to the fourth row number; and to prioritize the fourth level as the priority of the pre-selected column name corresponding to each row number.

[0145] In one possible design, a historical error summary table is pre-stored. The historical error summary table includes multiple rows of historical error data. Each row of historical error data includes a historical error column name and a historical pre-selected column name. The historical error column name is obtained from the business activation system.

[0146] Module 110 is used to obtain the error column name from the business activation system;

[0147] The priority confirmation module 130 is used to determine the target error data row from multiple historical error data rows based on the error column name, obtain the historical pre-selected column name of the target error data row, and the historical error count of the historical pre-selected column name of the target error data row, wherein the error column name is the same as the historical error column name of the target error data row; determine the target pre-selected column name from multiple pre-selected column names, wherein the target pre-selected column name is the same as the historical pre-selected column name of the target error data row; when the historical error count is greater than a preset third number, the first level is used as the priority of the target pre-selected column name; when the historical error count is not greater than the third number, and the priority of the target pre-selected column name is not the first level, the second level is used as the priority of the target pre-selected column name.

[0148] In one possible design, the sales system pre-stores a customer type table and a product attribute table. The customer type table includes a user identifier column name, and the product attribute table includes a product type column name.

[0149] The acquisition module 110 is used to associate the customer type table and the product attribute table based on the relationship between the user identifier column name and the product type column name, and obtain the sales system summary table.

[0150] In one possible design, the annotation module 140 is used to annotate the sales system data corresponding to each priority level in the sales system data corresponding to the newly added data row, based on the mapping relationship between priority and annotation color set.

[0151] This embodiment provides a column name error troubleshooting device that can execute a column name error troubleshooting method of the above embodiment. Its implementation principle and technical effect are similar, and will not be described again here.

[0152] In a specific implementation of the aforementioned column name error troubleshooting device, each module can be implemented as a processor. The processor can execute computer execution instructions stored in the memory, causing the processor to execute the aforementioned column name error troubleshooting method.

[0153] Figure 4 This is a schematic diagram of the hardware structure of the electronic device provided in an embodiment of this application. For example... Figure 4 As shown, the electronic device 200 includes at least one processor 210 and a memory 220. The electronic device 200 also includes a communication component 230. The processor 210, memory 220, and communication component 230 are connected via a bus 240.

[0154] In the specific implementation process, at least one processor 210 executes computer execution instructions stored in memory 220, causing at least one processor 210 to execute a column name error troubleshooting method as executed on the electronic device side as described above.

[0155] The specific implementation process of processor 210 can be found in the above method embodiments, and its implementation principle and technical effect are similar. Therefore, it will not be described again here.

[0156] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0157] The memory may include high-speed RAM, and may also include non-volatile storage (NVM), such as at least one disk storage.

[0158] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0159] The above description of the functions implemented by electronic devices and main control devices has introduced the solutions provided by the embodiments of the present invention. It is understood that, in order to implement the above functions, the electronic device or main control device includes hardware structures and / or software modules corresponding to the execution of each function. By combining the units and algorithm steps of the various examples described in the embodiments of the present invention, the embodiments of the present invention can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the technical solutions of the embodiments of the present invention.

[0160] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the above-described column name error troubleshooting method.

[0161] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0162] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in an electronic device or a host device.

[0163] This application also provides a computer program product, comprising: a computer program stored in a readable storage medium, wherein at least one processor of an electronic device can read the computer program from the readable storage medium, and the at least one processor executes the computer program to cause the electronic device to perform the scheme provided in any of the above embodiments.

[0164] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0165] The technical solutions of this application have been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it is readily understood by those skilled in the art that the scope of protection of this application is obviously not limited to these specific embodiments. The above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. These modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for troubleshooting column naming errors, characterized in that, The method includes: When the service activation of a new user fails, the sales system summary table is retrieved. The sales system summary table includes multiple rows of historical data and one row of new data. Each historical user corresponds to one historical data row, and the new user corresponds to the new data row. Each historical user refers to a user whose service activation was successful. Based on the newly added data row, at least one distinguishing data row is determined from the multiple historical data rows, wherein the cell data of a first number of pre-selected column names in each distinguishing data row is different from the corresponding cell data in the newly added data row; The priority of each preselected column name is obtained based on the number of rows of distinguishing data corresponding to each preselected column name, wherein the priority is used to indicate the probability of error in the cell data of each preselected column name in the newly added data row; In the sales system data corresponding to the newly added data row, the priority of the sales system data corresponding to each of the pre-selected column names is marked.

2. The method according to claim 1, characterized in that, The priorities include: a first level, a second level, a third level, and a fourth level that are positively correlated with the error probability of reverse sorting; The step of determining the priority of each preselected column name based on the number of rows of distinguishing data corresponding to each preselected column name includes: Reverse sort multiple rows to obtain the first row number and the second row number, where the first row number refers to the row number that is first in the reverse sort result, and the second row number refers to the row number that is second in the reverse sort result; Based on the second row number, the third row number is obtained, wherein the third row number is equal to the product of the second row number and the preset second quantity; When the number of the first row is greater than the number of the third row, the first level or the third level is used as the priority of the pre-selected column name corresponding to the number of the first row, and the second level or the fourth level is used as the priority of the pre-selected column name corresponding to the number of the fourth row, wherein the number of the fourth row refers to any one of the multiple row numbers other than the number of the first row; When the number of the first row is not greater than the number of the third row, the second level or the fourth level shall be used as the priority of the pre-selected column name corresponding to each row number.

3. The method according to claim 2, characterized in that, When the first quantity equals one, the step of prioritizing the first level or the third level as the priority of the pre-selected column name corresponding to the first row number, and prioritizing the second level or the fourth level as the priority of the pre-selected column name corresponding to the fourth row number, includes: The first level is used as the priority of the pre-selected column name corresponding to the first row number, and the second level is used as the priority of the pre-selected column name corresponding to the fourth row number; The step of prioritizing the second level or the fourth level as the pre-selected column name corresponding to each row number includes: The second level is used as the priority for the pre-selected column name corresponding to each row number.

4. The method according to claim 2, characterized in that, When the first quantity equals two, the step of prioritizing the first level or the third level as the priority of the pre-selected column name corresponding to the first row number, and prioritizing the second level or the fourth level as the priority of the pre-selected column name corresponding to the fourth row number, includes: The third level is used as the priority of the pre-selected column name corresponding to the first row number, and the fourth level is used as the priority of the pre-selected column name corresponding to the fourth row number; The step of prioritizing the second level or the fourth level as the pre-selected column name corresponding to each row number includes: The fourth level is used as the priority for the pre-selected column name corresponding to each row number.

5. The method according to claim 3 or 4, characterized in that, A historical error summary table is pre-stored. The historical error summary table includes multiple rows of historical error data. Each row of historical error data includes a historical error column name and a historical pre-selected column name. The historical error column name is obtained from the business activation system. Before marking the priority of each pre-selected column name in the sales system data corresponding to the newly added data row, the method further includes: Obtain the error column name from the service activation system; Based on the error column name, a target error data row is determined from the multiple historical error data rows, and the historical pre-selected column name of the target error data row and the historical error count of the historical pre-selected column name of the target error data row are obtained, wherein the error column name is the same as the historical error column name of the target error data row; A target preselected column name is determined from a variety of preselected column names, wherein the target preselected column name is the same as the historical preselected column name of the target error data row; When the number of historical error reports exceeds a preset third number, the first level is used as the priority of the target pre-selected column name; When the number of historical error reports is not greater than the third number, and the priority of the target pre-selected column name is not the first level, the second level shall be used as the priority of the target pre-selected column name.

6. The method according to claim 5, characterized in that, The sales system pre-stores a customer type table and a product attribute table. The customer type table includes a user identifier column name, and the product attribute table includes a product type column name. The process of obtaining the sales system summary table includes: Based on the association between the user identifier column name and the product type column name, the customer type table and the product attribute table are associated to obtain the sales system summary table.

7. The method according to claim 6, characterized in that, In the sales system data corresponding to the newly added data row, the priority of each pre-selected column name is marked, including: Based on the mapping relationship between the priority and the set of annotation colors, the sales system data corresponding to each priority is annotated in the sales system data corresponding to the newly added data row using the set of annotation colors.

8. A column name error troubleshooting device, characterized in that, The device includes: The acquisition module is used to acquire the sales system summary table when the service activation of a new user fails. The sales system summary table includes multiple historical data rows and one new data row. Each historical user corresponds to one historical data row, and the new user corresponds to the new data row. Each historical user refers to a user whose service activation was successful. The pre-selected column name module is used to determine at least one distinguishable data row from the multiple rows of historical data rows based on the newly added data row, wherein the cell data of a first number of pre-selected column names in each distinguishable data row is different from the corresponding cell data in the newly added data row. The priority confirmation module is used to obtain the priority of each preselected column name based on the number of rows of distinguishing data rows corresponding to each preselected column name, wherein the priority is used to indicate the error probability of cell data of each preselected column name in the newly added data row; The annotation module is used to annotate the priority of the sales system data corresponding to each of the pre-selected column names in the sales system data corresponding to the newly added data row.

9. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; When the processor executes the computer execution instructions stored in the memory, it is used to implement the column name error troubleshooting method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the column name error troubleshooting method as described in any one of claims 1 to 7.

Citation Information

Patent Citations

  • Dynamically detecting exceptions based on data changes

    US20080189639A1

  • Detecting errors in spreadsheets

    US20170337238A1