Field data processing method and related device

Abstract

Embodiments of the present application disclose a field data processing method and related equipment, which are used for field data processing in the case of avoiding invalidation of content configured by a client and improving product use experience of the client. The method comprises the following steps: obtaining a target standard table and a target extension table, the target standard table comprising target standard data of an extension field and target standard data of a standard field, and the target extension table comprising target extension data of the extension field; after obtaining a read request of target version data of a target field, determining whether the target field is an extension field; if the target field is an extension field, taking the target standard data of the target field in the target standard table or the target extension data of the target field in the target extension table as the target version data of the target field; and if the target field is a standard field, taking the target standard data of the target field in the target standard table as the target version data of the target field.

Description

Technical Field

[0001] This application relates to the field of field data processing, and more specifically, to field data processing methods, field data processing apparatus, computer equipment, computer-readable storage media, and computer program products containing instructions or computer programs. Background Technology

[0002] With the advancement of technology and the increase in business complexity, enterprise applications and services are becoming more diversified, and customers' demand for customized development of product functions is becoming more and more common. Therefore, a flexible field data processing method is needed.

[0003] The existing field data processing method is to overwrite the preset data of the target field with upgraded data or custom data during product upgrades or customer-customized secondary development (custom extension), thereby configuring the target field as upgraded data or custom data.

[0004] However, with existing field data processing methods, once the data is overwritten, it becomes impossible to retrieve (read) the previously configured data again, causing the customer's configuration to become invalid. If the requirement to retrieve the previously configured data for that field is to be met, re-development and configuration are required, resulting in a significant waste of time and resources and impacting the customer's use of the product. Summary of the Invention

[0005] This application provides a field data processing method, a field data processing apparatus, a computer device, a computer-readable storage medium, and a computer program product containing instructions or computer programs, which can perform field data processing while avoiding the invalidation of customer-configured content and improving the customer's product user experience.

[0006] In a first aspect, embodiments of this application provide a field data processing method, including:

[0007] Obtain the target standard table and the target extended table. The target standard table includes target standard data for the extended fields and target standard data for the standard fields. The target extended table includes target extended data for the extended fields.

[0008] After obtaining the read request for the target version data of the target field, determine whether the target field is an extended field;

[0009] If the target field is an extended field, then the target standard data of the target field in the target standard table or the target extended data of the target field in the target extended table shall be used as the target version data of the target field.

[0010] If the target field is a standard field, then the target standard data of the target field in the target standard table shall be used as the target version data of the target field.

[0011] Secondly, embodiments of this application provide a field data processing apparatus, including:

[0012] An acquisition unit is used to acquire a target standard table and a target extended table. The target standard table includes target standard data of extended fields and target standard data of standard fields. The target extended table includes target extended data of the extended fields.

[0013] The determining unit is used to determine whether the target field is an extended field after obtaining a read request for the target version data of the target field;

[0014] The determining unit is further configured to, if the target field is an extended field, use the target standard data of the target field in the target standard table or the target extended data of the target field in the target extended table as the target version data of the target field;

[0015] The determining unit is further configured to, if the target field is a standard field, use the target standard data of the target field in the target standard table as the target version data of the target field.

[0016] Thirdly, embodiments of this application provide a computer device, including:

[0017] Central processing unit, memory, input / output interfaces, wired or wireless network interfaces, and power supply;

[0018] The memory is either a short-term storage memory or a persistent storage memory;

[0019] The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the aforementioned field data processing method.

[0020] Fourthly, embodiments of this application provide a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the aforementioned field data processing method.

[0021] Fifthly, embodiments of this application provide a computer program product containing instructions that, when run on a computer, cause the computer to execute the aforementioned field data processing method.

[0022] As can be seen from the above technical solutions, the embodiments of this application have the following advantages: independent target standard tables and target extended tables can be obtained. Each of the target standard tables and target extended tables contains standard data and extended data of the extended fields. That is, multiple versions of extended field data can be retained at the same time. The content configured by the customer will not become invalid due to new version updates. Moreover, if it is necessary to meet the requirement of obtaining the previously configured data of the field, the corresponding version data can be obtained from the target standard table or the target extended table by determining whether the target field is an extended field. There is no need to redevelop and configure the same configuration requirements, which reduces repetitive development and configuration work, reduces time and resource consumption, and will not affect the use of the customer's product, resulting in a better user experience for the customer. Attached Figure Description

[0023] Figure 1 This is a schematic diagram of the architecture of a field data processing system disclosed in an embodiment of this application;

[0024] Figure 2 This is a flowchart illustrating a field data processing method disclosed in an embodiment of this application;

[0025] Figure 2-1 This is a schematic diagram of a target standard table and a target expansion table disclosed in an embodiment of this application;

[0026] Figure 3 This is a schematic diagram of another field data processing procedure disclosed in an embodiment of this application;

[0027] Figure 3-1 This is a schematic diagram of an initial standard table disclosed in an embodiment of this application;

[0028] Figure 3-2 This is a schematic diagram of an initial extended table disclosed in an embodiment of this application;

[0029] Figure 4 This is a schematic diagram illustrating another field data processing procedure disclosed in an embodiment of this application;

[0030] Figure 5 This is a flowchart illustrating another field data processing method disclosed in an embodiment of this application;

[0031] Figure 6 This is a schematic diagram of the structure of a field data processing device disclosed in an embodiment of this application;

[0032] Figure 7 This is a schematic diagram of the structure of a computer device disclosed in an embodiment of this application. Detailed Implementation

[0033] This application provides a field data processing method, a field data processing apparatus, a computer device, a computer-readable storage medium, and a computer program product containing instructions or computer programs, for processing field data while avoiding the invalidation of customer-configured content and improving the customer's product user experience.

[0034] This application can be applied to various information management systems, such as Enterprise Resource Planning (ERP), tax systems, financial systems, human resource systems, and supply chain systems.

[0035] Please see Figure 1 The architecture of the field data processing system 100 in this embodiment includes:

[0036] Computer device 101 (device for performing field data processing) and client (tenant / user) 102. When performing field data processing, computer device 101 can connect to client 102. Computer device 101 can obtain a target standard table and a target extended table. After receiving a read request for target version data of a target field sent by client 102, it can determine whether the target field is an extended field. If the target field is an extended field, it uses the target standard data of the target field in the target standard table or the target extended data of the target field in the target extended table as the target version data of the target field. If the target field is a standard field, it uses the target standard data of the target field in the target standard table as the target version data of the target field and returns the target version data of the target field to client 102.

[0037] based on Figure 1 Please refer to the field data processing system shown. Figure 2 , Figure 2 This is a flowchart illustrating a field data processing method disclosed in an embodiment of this application. The method includes:

[0038] 201. Obtain the target standard table and the target extended table. The target standard table includes the target standard data of the extended fields and the target standard data of the standard fields. The target extended table includes the target extended data of the extended fields.

[0039] When processing field data, you can obtain the target standard table and the target extended table. The target standard table includes the target standard data of the extended fields and the target standard data of the standard fields. The target extended table includes the target extended data of the extended fields.

[0040] It is important to understand that standard fields are used to represent non-extendable fields, while extended fields are used to represent fields that can be extended. The standard data of a field (standard field or extended field) is used to represent the data set at the factory (before or after product upgrade), while the extended data of an extended field is used to represent the extended data obtained by the user (tenant, such as company A) when customizing and extending the data of the extended field.

[0041] Specifically, for example, secondary development (custom extension) can refer to users modifying certain fields or filtering conditions (related fields) of the inventory accounting configuration form to meet specific needs. The inventory accounting configuration form is used to configure the inventory accounting that inventory documents need to participate in. The configuration form will configure the corresponding field identifiers of the inventory documents to obtain the document's conditions and other information, thereby enabling subsequent document processing.

[0042] To be more specific, please refer to an example. Figure 2-1 , Figure 2-1 This is a schematic diagram of a target standard table and a target expansion table disclosed in an embodiment of this application. Figure 2-1 It can be seen that "Expandable Field 1" and "Expandable Field 2" in the target standard table are extended fields, and "Field 1" and "Field 2" are standard fields. The target standard data of "Expandable Field 1" is "FX = 'B' and FY > 100", the target standard data of "Expandable Field 2" is "FY + 100", the target standard data of "Field 1" is "abcd", and the target standard data of "Field 2" is "123". In the target extended table, "Expandable Field 1" and "Expandable Field 2" are extended fields. The target extended data of "Expandable Field 1" is "FX = 'B' and FXE = '1'", and the target extended data of "Expandable Field 2" is "FY + 500".

[0043] 202. After obtaining the read request for the target version data of the target field, determine whether the target field is an extended field.

[0044] After obtaining the target standard table and the target extended table, you can obtain the read request for the target version data of the target field and then determine whether the target field is an extended field.

[0045] It is important to understand that target version data is used to represent either the target standard data or the target extended data.

[0046] 203. If the target field is an extended field, then the target standard data of the target field in the target standard table or the target extended data of the target field in the target extended table shall be used as the target version data of the target field.

[0047] After determining whether the target field is an extended field, if the target field is an extended field, then the target standard data of the target field in the target standard table or the target extended data of the target field in the target extended table shall be used as the target version data of the target field.

[0048] Specifically, for example, if the target field is "Expandable Field 1", which is an extended field, then the target standard data "FX='B'and FY>100" of "Expandable Field 1" in the target standard table or the target extended data "FX='B'And FXE='1'" of "Expandable Field 1" in the target extended table can be used as the target version data of "Expandable Field 1".

[0049] To facilitate understanding of the embodiments of this application, the following specific example illustrates the differences between the embodiments of this application and the prior art:

[0050] The existing field data processing method (configuring field data through overwriting) allows customers (users) to directly overwrite the original data when they need to customize and extend a field's data (customized secondary development configuration). Similarly, during product upgrades, the upgraded data can overwrite the custom data. However, once the data is overwritten, the previously configured data cannot be retrieved, rendering the customer's configuration invalid. If the customer needs to use the previously configured custom data for that field, re-development and configuration are required, resulting in significant time and resource consumption and impacting the customer's product usage.

[0051] In this embodiment, the target standard table and the target extended table can be maintained separately, achieving separate data management and version control. Through independent target standard and target extended tables, data from all versions prior to the extended field (including standard and extended data before / after upgrades) can be retained simultaneously for users to select and retrieve (read). This means that the customer's configuration will not become invalid due to new version updates. Furthermore, if the requirement to retrieve previously configured data for a field is needed, the system can determine whether the target field is an extended field and selectively retrieve the corresponding version data from either the target standard or target extended table. This eliminates the need to redevelop and configure the same settings, reducing repetitive development and configuration work, saving time and resources, and ensuring no impact on the customer's product usage, resulting in a better user experience.

[0052] 204. If the target field is a standard field, then the target standard data of the target field in the target standard table will be used as the target version data of the target field.

[0053] After determining whether the target field is an extended field, if the target field is a standard field, then the target standard data of the target field in the target standard table is used as the target version data of the target field.

[0054] Specifically, for example, if the target field is "Field 1", which is a standard field, then the target standard data "abcd" of "Field 1" in the target standard table can be used as the target version data of "Field 1".

[0055] In this embodiment, independent target standard tables and target extended tables can be obtained. Each target standard table and target extended table contains standard data and extended data of extended fields. This means that multiple versions of extended field data can be retained simultaneously. The content configured by the customer will not become invalid due to new version updates. Furthermore, if the requirement to obtain previously configured data for a field is to be met, the corresponding version data can be obtained from the target standard table or the target extended table by determining whether the target field is an extended field. This eliminates the need to redevelop and configure the same configuration requirements, reduces repetitive development and configuration work, reduces time and resource consumption, and does not affect the customer's product usage, resulting in a better customer product user experience.

[0056] based on Figure 2 The described embodiment, during field data processing, can retain multiple versions of extended field data simultaneously through independent target standard tables and target extended tables. This ensures that customer-configured content remains valid despite version updates and provides corresponding version data, reducing repetitive development and configuration work, saving time and resources, and improving the customer's product experience to some extent. However, in product upgrade scenarios or scenarios requiring multiple custom extensions of a field, customer-configured content may still become invalid, necessitating repeated development and configuration, thus impacting product usage. To address these issues, a detailed implementation example of this solution is provided below. Please refer to [link / reference]. Figure 3 , Figure 3 This is a schematic diagram of another field data processing process disclosed in an embodiment of this application. Another embodiment of the field data processing method of this application includes:

[0057] 301. Create an initial standard table. Based on the update requests of the initial standard data of the extended fields and the standard fields, update the initial standard data of the extended fields and the initial standard data of the standard fields in the initial standard table to the target standard data of the extended fields and the target standard data of the standard fields to obtain the target standard table.

[0058] When processing field data, an initial standard table can be created first. Then, based on the update requests of the initial standard data of the extended fields and the standard fields, the initial standard data of the extended fields and the initial standard data of the standard fields in the initial standard table can be updated to the target standard data of the extended fields and the target standard data of the standard fields to obtain the target standard table.

[0059] For specific examples, please refer to [link / reference]. Figure 3-1 , Figure 3-1 This is a schematic diagram of an initial standard table disclosed in an embodiment of this application. Figure 3-1 It can be seen that "Expandable Field 1" and "Expandable Field 2" in the initial standard table are extended fields, and "Field 1" and "Field 2" are standard fields. The initial standard data of "Expandable Field 1" is "FX='B'", the initial standard data of "Expandable Field 2" is "FY+100", the initial standard data of "Field 1" is "abc", and the initial standard data of "Field 2" is "123". After obtaining the upgrade request of "Expandable Field 1" and "Field 2", the initial standard data of "Expandable Field 1" can be updated from "FX='B'" to "FX='B'and FY>100" and the initial standard data of "Field 1" from "abc" to "abcd" according to the upgrade request.

[0060] It is worth mentioning that when the product is upgraded, only the initial standard data of the extended field in the initial standard table is updated to the target standard data, and the extended data of the extended field in the extended table is not modified. Therefore, the extended data of the extended field is still retained. Thus, for product upgrade scenarios, this application embodiment does not require repeated development and configuration, thereby reducing time and resource consumption, and will not affect the customer's product use, resulting in a better customer product experience.

[0061] 302. Create an initial extended table. Based on the update request of the initial extended data of the extended fields, update the initial extended data of the extended fields in the initial extended table to the target extended data of the extended fields to obtain the target extended table.

[0062] An initial extended table can be created. Based on the update request of the initial extended data of the extended fields, and based on the update extended data of the extended fields, the initial extended data of the extended fields in the initial extended table can be updated to the target extended data of the extended fields to obtain the target extended table.

[0063] It is worth mentioning that when a certain field needs to be customized and extended multiple times, the initial extended data of the extended field in the initial extended table is only updated to the target extended data, and the standard data of the extended field in the standard table is not modified. Therefore, the standard data of the extended field is still retained. Thus, for scenarios where a certain field needs to be customized and extended multiple times, this application embodiment does not require repeated development and configuration. Therefore, it reduces time and resource consumption, does not affect the use of the customer's product, and provides a better user experience for the customer's product.

[0064] One method for updating the initial extended data of an extended field in the initial extended table to the target extended data of the extended field based on the updated extended data of the extended field is to use the updated extended data of the extended field as the target extended data of the extended field, or to combine the initial extended data of the extended field and the updated extended data of the extended field, and use the combined data as the target extended data of the extended field.

[0065] Specifically, "using the updated extended data of the extended field as the target extended data of the extended field" is an overwrite (replacement) method. For an example, please refer to [link to example]. Figure 3-2 , Figure 3-2 This is a schematic diagram of an initial extended table disclosed in an embodiment of this application. Figure 3-2 It is known that the initial extended data of "Expandable Field 1" in the initial extended table is "FX = 'B' And FXE = '2'". The updated extended data of "Expandable Field 1" "FX = 'B' And FXE = '1'" can be used as the target extended data of the extended field to obtain the target extended table. "Combining the initial extended data and the updated extended data of the extended field, and using the combined data as the target extended data of the extended field" is an appending method. For example, the initial extended data of "Expandable Field 1" "FX = 'B' And FXE = '2'" and the updated extended data of "Expandable Field 1" "FX = 'B' And FXE = '1'" can be combined, and the combined data can be used as the target extended data of "Expandable Field 1".

[0066] It is worth mentioning that the method of overwriting / appending extended data can provide diversity and feasibility for updating extended data of extended fields in the initial extended table, and improve the diversity of extended version data.

[0067] 303. After obtaining the read request for the target version data of the target field, determine whether the target field is an extended field.

[0068] 304. If the target field is an extended field, then the target standard data of the target field in the target standard table or the target extended data of the target field in the target extended table shall be used as the target version data of the target field.

[0069] 305. If the target field is a standard field, then the target standard data of the target field in the target standard table shall be used as the target version data of the target field.

[0070] Steps 303 to 305 in this embodiment are the same as those described above. Figure 2 Steps 202 to 204 in the illustrated embodiment are similar and will not be repeated here.

[0071] It is worth mentioning that in existing field data processing methods, if a customer needs to retrieve previously customized secondary development configuration data for a particular field, the same customized secondary development requirement needs to be repeatedly configured after each upgrade. This results in low field configuration efficiency, especially with multiple upgrades, where the same customized secondary development requirement needs to be repeatedly configured multiple times. Therefore, field configuration efficiency and field data processing efficiency are particularly low. In this embodiment, however, if a customer needs to retrieve previously customized secondary development configuration data for a particular field, regardless of whether there is one or multiple upgrades, the upgraded data and the customer's customized secondary development configuration data can be retained simultaneously. This avoids the need for repeated configuration of the same customized secondary development requirement during multiple upgrades, resulting in higher field configuration efficiency. Especially during multiple upgrades, this avoids the repeated configuration of the same customized secondary development requirement seen in existing technologies. Therefore, this embodiment has higher field configuration efficiency and higher field data processing efficiency.

[0072] In this embodiment, independent target standard tables and target extended tables can be obtained. Each target standard table and target extended table contains standard data and extended data for extended fields. This means that multiple versions of extended field data can be retained simultaneously, and the customer's configuration will not become invalid due to new version updates. Furthermore, if the requirement to retrieve previously configured data for a field is needed, the corresponding version data can be retrieved from the target standard table or target extended table by determining whether the target field is an extended field. This eliminates the need to redevelop and configure the same configuration requirements, reducing redundant development and configuration work, reducing time and resource consumption, and not affecting the customer's product usage, resulting in a better customer product experience. Secondly, when the product is upgraded, only the initial standard data of the extended field in the initial standard table is updated to the target standard data. The extended data of the extended field in the extended table is not modified, and the extended data of the extended field is still retained. This eliminates the need for repeated development and configuration, thus reducing time and resource consumption, not affecting the customer's product usage, and resulting in a better customer product experience. Next, when a field needs to be customized and extended multiple times, only the initial extended data of the extended field in the initial extended table is updated to the target extended data. The standard data of the extended field in the standard table is not modified; it is still retained. Therefore, repeated development and configuration are unnecessary, reducing time and resource consumption and not affecting the customer's product usage, resulting in a better user experience. Furthermore, the method of overwriting / appending extended data provides diversity and feasibility for updating the extended data of extended fields in the initial extended table, and increases the diversity of extended version data, improving the variety of version data available to users and enhancing the user experience. Finally, if there is a customer need to retrieve previously customized secondary development configuration data for this field, whether it is a single upgrade or multiple upgrades, the upgraded data and the customer's customized secondary development configuration data can be retained simultaneously. Repeated configuration for the same customized secondary development needs is not required, resulting in high efficiency in field configuration and field data processing.

[0073] based on Figure 2 The described embodiment, while allowing for the retention of multiple versions of extended fields through independent target standard tables and target extended tables during field data processing, ensures that customer-configured content remains valid despite version updates and provides corresponding version data. This reduces repetitive development and configuration work, saves time and resources, and improves the customer's product experience to some extent. However, there may be instances where the returned version data does not match the required version data, leading to inaccurate field data version returns. To address this issue, a detailed embodiment of this solution, which can be selectively implemented, is provided below. Please refer to [link / reference]. Figure 4 , Figure 4 This is a flowchart illustrating another field data processing method disclosed in this application. Another embodiment of the field data processing method of this application includes:

[0074] 401. Obtain the target standard table and the target extended table. The target standard table includes the target standard data of the extended fields and the target standard data of the standard fields. The target extended table includes the target extended data of the extended fields.

[0075] 402. After obtaining the read request for the target version data of the target field, determine whether the target field is an extended field.

[0076] Steps 401 to 402 in this embodiment are the same as those described above. Figure 2 Steps 201 to 202 in the illustrated embodiment are similar and will not be repeated here.

[0077] 403. If the target field is an extended field and the target version data is standard version data, then the target standard data of the target field in the target standard table shall be used as the target version data of the target field. If the target version data is an extended version data, then the target extended data of the target field in the target extended table shall be used as the target version data of the target field.

[0078] Specifically, for example, if the target field is "Expandable Field 1" and the target version data is standard version data, then "FX = 'B' and FY > 100" in the target standard table "Expandable Field 1" will be used as the target version data of "Expandable Field 1". If the target version data is extended version data, then "FX = 'B' and FXE = '1'" in the target extended table "Expandable Field 1" will be used as the target version data of "Expandable Field 1".

[0079] If the target extension table includes target extension data that extends the target field N times, where 1≤N, and the target version data is the nth extension data of the nth extension of the target field, where 1≤n≤N, then the method of using the target extension data of the target field in the target extension table as the target version data of the target field can be to use the nth extension data of the target field in the target extension table as the target version data of the target field.

[0080] It is understandable that the Nth expansion of the Nth expansion is the latest version of the data, and the larger n is, the newer the version of the Nth expansion. Specifically, for example, if the target field is "expandable field 1", and the target expansion table includes target expansion data that expands "expandable field 1" three times, including the first expansion data "FX='B'And FXE='2'", the second expansion data "FX='B'And FXE='3'", and the third expansion data "FX='B'And FXE='1'", and if the target version data is the Nth expansion of "expandable field 1", then the Nth expansion data (the latest version of the data) of "expandable field 1" in the target expansion table can be used as the target version data of "expandable field 1".

[0081] It is worth mentioning that for extended fields, if the required data is the standard version, the standard version data will be returned; if the required data is the extended version, the extended version data will be returned; and if the required data is the nth extended version, the nth extended version data will be returned. In other words, it can return the version data corresponding to the target version data, and the accuracy of the returned field data version is relatively high.

[0082] 404. If the target field is a standard field, then the target standard data of the target field in the target standard table will be used as the target version data of the target field.

[0083] Step 404 in this embodiment is the same as described above. Figure 2 Step 204 in the illustrated embodiment is similar and will not be repeated here.

[0084] In this embodiment, independent target standard tables and target extended tables can be obtained. Each target standard table and target extended table contains standard data and extended data for extended fields. This means that multiple versions of extended field data can be retained simultaneously, ensuring that customer-configured content does not become invalid due to new version updates. Furthermore, if the requirement to retrieve previously configured data for a field is needed, the corresponding version data can be retrieved from either the target standard table or the target extended table by determining whether the target field is an extended field. This eliminates the need to redevelop and configure the same configuration requirements, reducing redundant development and configuration work, saving time and resources, and ensuring no impact on the customer's product usage, resulting in a better user experience. Secondly, for extended fields, if standard version data is required, standard version data is returned; if extended version data is required, extended version data is returned; if the nth extended version data is required, the nth extended version data is returned. In other words, the version data corresponding to the required target version data can be returned, ensuring high accuracy in returning field data versions.

[0085] based on Figure 2 , Figure 3 and Figure 4 Building upon this, to improve the accuracy and efficiency of determining whether a target field is an extended field, this can be achieved by setting and utilizing the extended field's extended identifier. For details on how to implement this, please refer to the following description:

[0086] Before obtaining the target standard table and the target extended table, the extension identifier of the extended field can be set. The method to determine whether the target field is an extended field can be based on the extension identifier of the target field.

[0087] Specifically, for a better understanding of the embodiments of this application, please refer to [link / reference]. Figure 5 , Figure 5 This is a flowchart illustrating another field data processing method disclosed in an embodiment of this application. Figure 5 It can be seen that the field data processing process includes two stages: design time and runtime.

[0088] 1. Design time phase: For each extended field, add an "Extendable" attribute option to set the extension identifier of the extended field;

[0089] 2. Runtime phase:

[0090] (1) Data reading stage: For extended fields with extended identifiers, the corresponding extended field can be found in the extended table through the extended identifier, and the data of the row with the largest version number can be read. If the data of the extended field is not empty, the data of the extended field is returned; otherwise, the data of the standard field is read and returned.

[0091] (2) Data modification stage: For extended fields with extended identifiers set, the front-end (client) can provide an operation button for extending modification on the right side of the extended field control. When the field is modifiable, clicking the button will modify the field content in the pop-up interface. Modification supports overwriting and appending. Appending means adding an extended row and incrementing the maximum version number by 1, but it cannot overwrite the data of the standard original version (the standard data of the extended field in the standard table).

[0092] (3) Data saving stage: For extended fields with extended identifiers, determine whether the extended field exists in the extended table. If it does not exist, create the extended field and then save the field content according to the settings in the "data modification stage".

[0093] It is understandable that, in addition to the method of distinguishing between old and new versions of data by version number as described above, other reasonable methods such as timestamps can also be used, which are not limited here.

[0094] It is worth mentioning that by setting an extension identifier for the extended field and determining whether the target field is an extended field based on the extension identifier of the target field, the accuracy and efficiency of determining whether the target field is an extended field can be improved.

[0095] The field data processing method in the embodiments of this application has been described above. The field data processing apparatus in the embodiments of this application is described below. Please refer to [link / reference]. Figure 6 One embodiment of the field data processing device in this application includes:

[0096] An acquisition unit is used to acquire a target standard table and a target extended table. The target standard table includes target standard data of extended fields and target standard data of standard fields. The target extended table includes target extended data of the extended fields.

[0097] The determining unit is used to determine whether the target field is an extended field after obtaining a read request for the target version data of the target field;

[0098] The determining unit is further configured to, if the target field is an extended field, use the target standard data of the target field in the target standard table or the target extended data of the target field in the target extended table as the target version data of the target field;

[0099] The determining unit is further configured to, if the target field is a standard field, use the target standard data of the target field in the target standard table as the target version data of the target field.

[0100] The acquisition unit is specifically used to create an initial standard table, which includes the initial standard data of the extended field and the initial standard data of the standard field. According to the update request of the initial standard data of the extended field and the initial standard data of the standard field, the initial standard data of the extended field and the initial standard data of the standard field in the initial standard table are updated to the target standard data of the extended field and the target standard data of the standard field to obtain the target standard table.

[0101] The acquisition unit is specifically used to create an initial extended table, which includes the initial extended data of the extended field. Based on the update request of the initial extended data of the extended field, and based on the update extended data of the extended field, the initial extended data of the extended field in the initial extended table is updated to the target extended data of the extended field to obtain the target extended table.

[0102] The acquisition unit is specifically used to use the updated extended data of the extended field as the target extended data of the extended field, or to combine the initial extended data of the extended field and the updated extended data of the extended field, and use the combined data as the target extended data of the extended field.

[0103] The determining unit is specifically configured to, if the target version data is standard version data, use the target standard data of the target field in the target standard table as the target version data of the target field; and if the target version data is extended version data, use the target extended data of the target field in the target extended table as the target version data of the target field.

[0104] The determining unit is specifically used to take the nth extended data of the target field in the target extended table as the target version data of the target field. The target extended table includes target extended data that extends the target field N times, where 1 ≤ N. The target version data is the nth extended data of the nth extension of the target field, where 1 ≤ n ≤ N.

[0105] The field data processing device further includes:

[0106] The setting unit is used to set the extended identifier of the extended field;

[0107] The determining unit is specifically used to determine whether the target field is an extended field based on the extended identifier of the target field.

[0108] In this embodiment, independent target standard tables and target extended tables can be obtained. Each target standard table and target extended table contains standard data and extended data of extended fields. This means that multiple versions of extended field data can be retained simultaneously. The content configured by the customer will not become invalid due to new version updates. Furthermore, if the requirement to obtain previously configured data for a field is to be met, the corresponding version data can be obtained from the target standard table or the target extended table by determining whether the target field is an extended field. This eliminates the need to redevelop and configure the same configuration requirements, reduces repetitive development and configuration work, reduces time and resource consumption, and does not affect the customer's product usage, resulting in a better customer product user experience.

[0109] Please refer to the following: Figure 7 One embodiment of the computer device 700 in this application includes:

[0110] Central processing unit 701, memory 705, input / output interface 704, wired or wireless network interface 703, and power supply 702;

[0111] Memory 705 is either a short-term storage memory or a persistent storage memory;

[0112] The central processing unit 701 is configured to communicate with the memory 705 and execute instructions stored in the memory 705 to perform the aforementioned operations. Figure 2 , Figure 3 and Figure 4 The method in the illustrated embodiment.

[0113] This application also provides a computer-readable storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the aforementioned actions. Figure 2 , Figure 3 and Figure 4 The method in the illustrated embodiment.

[0114] This application also provides a computer program product containing instructions, which, when run on a computer, causes the computer to perform the aforementioned... Figure 2 , Figure 3 and Figure 4 The method in the illustrated embodiment.

[0115] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0116] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0117] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0118] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0119] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0120] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A method for processing field data, characterized in that, include: Obtain a target standard table and a target extended table. The target standard table includes target standard data for extended fields and target standard data for standard fields. The target extended table includes target extended data for the extended fields. The target standard data for the extended fields is used to characterize the data set at the factory for the extended fields. The target standard data for the standard fields is used to characterize the data set at the factory for the standard fields. The target extended data for the extended fields is used to characterize the extended data obtained when the user customizes and extends the data of the extended fields. After obtaining the read request for the target version data of the target field, determine whether the target field is an extended field; If the target field is an extended field, then the target standard data of the target field in the target standard table or the target extended data of the target field in the target extended table shall be used as the target version data of the target field. If the target field is a standard field, then the target standard data of the target field in the target standard table shall be used as the target version data of the target field; The acquisition of the target standard table and the target extended table includes: Obtain the initial standard table and the initial extended table; When the product is upgraded, the initial standard data of the target extended field in the initial standard table is updated to the target standard data only, and the extended data of the target extended field in the initial extended table is not modified; and / or when the target extended field is customized multiple times, the initial extended data of the target extended field in the initial extended table is updated to the target extended data only, and the standard data of the target extended field in the initial standard table is not modified, so as to obtain the target standard table and the target extended table.

2. The method according to claim 1, characterized in that, The acquisition of the target standard table includes: Create an initial standard table, which includes the initial standard data of the extended fields and the initial standard data of the standard fields; Based on the update request of the initial standard data of the extended field and the standard field, the initial standard data of the extended field and the initial standard data of the standard field in the initial standard table are updated to the target standard data of the extended field and the target standard data of the standard field to obtain the target standard table.

3. The method according to claim 1, characterized in that, The process of obtaining the target extended table includes: Create an initial extended table, which includes the initial extended data of the extended fields; Based on the update request of the initial extended data of the extended field, and based on the updated extended data of the extended field, the initial extended data of the extended field in the initial extended table is updated to the target extended data of the extended field to obtain the target extended table.

4. The method according to claim 3, characterized in that, The step of updating the extended data based on the extended field, which updates the initial extended data of the extended field in the initial extended table to the target extended data of the extended field, includes: Use the updated extended data of the extended field as the target extended data of the extended field; or The initial extended data and the updated extended data of the extended field are combined, and the combined data is used as the target extended data of the extended field.

5. The method according to any one of claims 1 to 4, characterized in that, The step of using the target standard data of the target field in the target standard table or the target extended data of the target field in the target extended table as the target version data of the target field includes: If the target version data is standard version data, then the target standard data of the target field in the target standard table shall be used as the target version data of the target field; If the target version data is extended version data, then the target extended data of the target field in the target extended table is used as the target version data of the target field.

6. The method according to claim 5, characterized in that, The target extension table includes target extension data that expands the target field N times, where 1 ≤ N, and the target version data is the nth extension data of the nth expansion of the target field, where 1 ≤ n ≤ N. The step of using the target extended data of the target field in the target extended table as the target version data of the target field includes: The nth extended data of the target field in the target extended table is used as the target version data of the target field.

7. The method according to any one of claims 1 to 4, characterized in that, Before obtaining the target standard table and the target extended table, the method further includes: Set the extension identifier for the extended field; Determining whether the target field is an extended field includes: Based on the extended identifier of the target field, determine whether the target field is an extended field.

8. A field data processing device, characterized in that, include: The acquisition unit is used to acquire a target standard table and a target extended table. The target standard table includes target standard data of extended fields and target standard data of standard fields. The target extended table includes target extended data of the extended fields. The target standard data of the extended fields is used to characterize the data set at the factory for the extended fields. The target standard data of the standard fields is used to characterize the data set at the factory for the standard fields. The target extended data of the extended fields is used to characterize the extended data acquired by the user when customizing the data of the extended fields. The determining unit is used to determine whether the target field is an extended field after obtaining a read request for the target version data of the target field; The determining unit is further configured to, if the target field is an extended field, use the target standard data of the target field in the target standard table or the target extended data of the target field in the target extended table as the target version data of the target field; The determining unit is further configured to, if the target field is a standard field, use the target standard data of the target field in the target standard table as the target version data of the target field; The acquisition unit is specifically used to acquire an initial standard table and an initial extended table. When the product is upgraded, the initial standard data of the target extended field in the initial standard table is updated to the target standard data only, without modifying the extended data of the target extended field in the initial extended table; and / or when multiple custom extensions are performed on the target extended field, the initial extended data of the target extended field in the initial extended table is updated to the target extended data only, without modifying the standard data of the target extended field in the initial standard table, so as to obtain the target standard table and the target extended table.

9. A computer device, characterized in that, include: Central processing unit and memory; The memory is either a short-term storage memory or a persistent storage memory; The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 7.

11. A computer program product comprising instructions or a computer program, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1 to 7.

Images