Field data processing method and related equipment

Abstract

The embodiment of the invention discloses a field data processing method and related equipment, which are used for performing field data processing under the conditions of avoiding the failure of content configured by a client and improving the product use experience of the client. The method comprises the steps that a target standard table and a target extension table are obtained, the target standard table comprises target standard data of an extension field and target standard data of a standard field, the target extension table comprises target extension data of the extension field, and after a reading request of target version data of the target field is obtained, the target version data of the target field is read; determining whether the target field is an extension field, if the target field is the extension field, taking target standard data of the target field in the target standard table or target extension data of the target field in the target extension table as target version data of the target field, and if the target field is the standard field, taking the target version data of the target field in the target extension table as target version data of the target field. And if yes, 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] The embodiments of the present application relate to the field of field data processing, and more specifically, to a field data processing method, a field data processing apparatus, a computer device, a computer-readable storage medium, and a computer program product including instructions or a computer program. Background Art

[0002] With the advancement of technology and the increase in business complexity, enterprise applications and services are becoming more and 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 the upgrade data or custom data during product upgrade or customer customized secondary development (custom extension), thereby configuring the target field as the upgrade data or custom data.

[0004] However, for the existing field data processing methods, after the data is overwritten, the previously configured data cannot be obtained (read) again, resulting in the invalidation of the customer's configured content. If the demand for obtaining the previously configured data of the field is to be met, re-development and configuration are required, resulting in a large amount of time and resource consumption, which affects the customer's use of the product. Summary of the invention

[0005] The embodiments of the present application provide a field data processing method, a field data processing apparatus, a computer device, a computer-readable storage medium, and a computer program product comprising instructions or a computer program, which can perform field data processing while avoiding the invalidation of content configured by a customer and improving the customer's product usage experience.

[0006] In a first aspect, an embodiment of the present application provides a field data processing method, including:

[0007] Acquire a target standard table and a target extension table, wherein the target standard table includes target standard data of an extension field and target standard data of a standard field, and the target extension table includes target extension data of the extension field;

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

[0009] If the target field is an extended field, 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 are used as the target version data of the target field;

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

[0011] In a second aspect, an embodiment of the present application provides a field data processing device, including:

[0012] an acquisition unit, configured to acquire a target standard table and a target extension table, wherein the target standard table includes target standard data of an extension field and target standard data of a standard field, and the target extension table includes target extension data of the extension field;

[0013] a determination unit, configured to determine whether the target field is an extended field after obtaining a read request for target version data of the target field;

[0014] The determining unit is further configured to use, if the target field is an extension field, 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;

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

[0016] In a third aspect, an embodiment of the present application provides a computer device, including:

[0017] CPU, memory, input and output interfaces, wired or wireless network interfaces, and power supply;

[0018] The memory is 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] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which includes instructions. When the instructions are executed on a computer, the computer executes the aforementioned field data processing method.

[0021] In a fifth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when the computer program product is run on a computer, enables the computer to execute the aforementioned field data processing method.

[0022] It can be seen from the above technical scheme that the embodiments of the present application have the following advantages: independent target standard tables and target extension tables can be obtained, and the target standard tables and target extension tables each contain standard data and extension data of the extension fields, that is, multiple versions of data of the extension fields can be retained at the same time, and the customer-configured content will not become invalid due to the new version update. In addition, if the need to obtain the data previously configured for the field is to be met, the corresponding version data can be obtained from the target standard table or the target extension table in a targeted manner by determining whether the target field is an extension field. There is no need to redevelop and configure the same configuration requirements, which reduces repeated development and configuration work, reduces time and resource consumption, and will not affect the customer's product use. The customer's product experience is better. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0024] Figure 2 A flowchart of a field data processing method disclosed in an embodiment of the present application;

[0025] Figure 2-1 A schematic diagram of a target standard table and a target extension table disclosed in an embodiment of the present application;

[0026] Figure 3 A schematic diagram of another process flow of field data processing disclosed in an embodiment of the present application;

[0027] Figure 3-1 A schematic diagram of an initial standard table disclosed in an embodiment of the present application;

[0028] Figure 3-2 A schematic diagram of an initial extension table disclosed in an embodiment of the present application;

[0029] Figure 4 A schematic diagram of a flow chart of another field data processing disclosed in an embodiment of the present application;

[0030] Figure 5 A flowchart of another field data processing method disclosed in an embodiment of the present application;

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

[0032] Figure 7 A schematic diagram of the structure of a computer device disclosed in an embodiment of the present application. DETAILED DESCRIPTION

[0033] The embodiments of the present application provide a field data processing method, a field data processing apparatus, a computer device, a computer-readable storage medium, and a computer program product comprising instructions or a computer program, for performing field data processing while avoiding the invalidation of content configured by a customer and improving the customer's product usage experience.

[0034] The present application can be applied to various information management systems, such as enterprise resource planning systems (ERP), tax systems, financial systems, human resources systems, supply chain systems, etc.

[0035] See also Figure 1 In the embodiment of the present application, the architecture of the field data processing system 100 includes:

[0036] Computer device (device for performing field data processing) 101 and client (tenant / user) 102. When performing field data processing, computer device 101 can be connected to client 102. Computer device 101 can obtain a target standard table and a target extension table, and after obtaining a read request for target version data of a target field sent by client 102, determine whether the target field is an extension field. If the target field is an extension field, use 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. 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, and return the target version data of the target field to client 102.

[0037] based on Figure 1 See the field data processing system shown in Figure 2 , Figure 2 The following is a flow chart of a field data processing method disclosed in an embodiment of the present application, wherein the method comprises:

[0038] 201. Obtain a target standard table and a target extension table, wherein the target standard table includes target standard data of an extension field and target standard data of a standard field, and the target extension table includes target extension data of the extension field.

[0039] When processing field data, a target standard table and a target extension table may be obtained. The target standard table includes target standard data of extension fields and target standard data of standard fields. The target extension table includes target extension data of extension fields.

[0040] It should be understood that standard fields are used to represent non-extensible fields, extended fields are used to represent extensible fields, the standard data of a field (standard field or extended field) is used to represent the data set for the field (standard field or extended field) at the factory (before or after product upgrade), and the extended data of an extended field is used to represent the extended data obtained by a user (tenant, such as Company A, etc.) when performing a customized extension to the data of an extended field.

[0041] Specifically, for example, secondary development (custom extension) can mean that users modify certain fields or filter conditions (involving fields) of the inventory accounting configuration sheet to meet specific demand scenarios. The inventory accounting configuration sheet is used to configure the inventory accounting that the inventory document needs to participate in. The configuration sheet will configure the corresponding field identifiers of the inventory document to obtain the conditions and other contents of the document for subsequent document processing.

[0042] For more specific examples, see Figure 2-1 , Figure 2-1 A schematic diagram of a target standard table and a target extension table disclosed in an embodiment of the present application, comprising Figure 2-1 It can be seen that "Extensible Field 1" and "Extensible Field 2" of the target standard table are extended fields, "Field 1" and "Field 2" are standard fields, the target standard data of "Extensible Field 1" is "FX='B'andFY>100", the target standard data of "Extensible Field 2" is "FY+100", the target standard data of "Field 1" is "abcd", and the target standard data of "Field 2" is "123", and "Extensible Field 1" and "Extensible Field 2" of the target extended table are extended fields, the target extended data of "Extensible Field 1" is "FX='B'And FXE='1'", and the target extended data of "Extensible Field 2" is "FY+500".

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

[0044] After obtaining the target standard table and the target extended table, a read request for the target version data of the target field may be obtained to determine whether the target field is an extended field.

[0045] It should be understood that the target version data is used to represent any one of the target standard data and the target extended data.

[0046] 203. If the target field is an extended field, 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 is used as the target version data of the target field.

[0047] After determining whether the target field is an extension field, if the target field is an extension field, 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 is used as the target version data of the target field.

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

[0049] To facilitate understanding of the embodiments of the present application, a specific example is given below to illustrate the difference between the embodiments of the present application and the prior art:

[0050] For the existing field data processing method (field data configuration by overwriting), when the customer (user) needs to customize and expand a field data (customized secondary development configuration), the custom data of the field can be directly overwritten with the original data. When the product is upgraded, the upgraded data of the field can be directly overwritten with the custom data. However, after the data is overwritten, the previously configured data cannot be obtained again, resulting in the invalidation of the customer's configuration. If the customer needs to use the custom data previously configured in the field, it is necessary to re-develop and reconfigure, resulting in a large amount of time and resource consumption, and affecting the customer's product use.

[0051] As for the embodiment of the present application, the target standard table and the target extension table can be maintained separately, realizing the separate management and version control of data. Through the independent target standard table and target extension table, the data of all versions before the extension field (including the standard data and extension data before / after the upgrade) can be retained at the same time for the user to choose to obtain (read), that is, the content configured by the customer will not be invalidated due to the new version update, and if the need to obtain the data configured before the field is to be met, the corresponding version data can be obtained from the target standard table or the target extension table in a targeted manner by determining whether the target field is an extension field, without the need to redevelop and configure the same configuration requirements, reducing repeated development and configuration work, reducing time and resource consumption, and will not affect the customer's product use, and the customer's product use experience is better.

[0052] 204. If the target field is a standard field, the target standard data of the target field in the target standard table is 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, 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, 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 an embodiment of the present application, an independent target standard table and a target extension table can be obtained. The target standard table and the target extension table each contain standard data and extended data of the extension field, that is, multiple versions of data of the extension field can be retained at the same time, and the customer's configured content will not become invalid due to the new version update. If the need to obtain the data previously configured for the field is to be met, the corresponding version data can be obtained from the target standard table or the target extension table in a targeted manner by determining whether the target field is an extension field. There is no need to redevelop and configure the same configuration requirements, which reduces repeated development and configuration work, reduces time and resource consumption, does not affect the customer's product usage, and the customer's product usage experience is better.

[0056] based on Figure 2 In the described embodiment, during the process of field data processing, although multiple versions of the extended field data can be retained through independent target standard tables and target extension tables, the customer-configured content will not become invalid due to new version updates, and the corresponding version data can be provided, reducing repeated development and configuration work, reducing time and resource consumption, and improving the customer's product experience to a certain extent. However, for product upgrade scenarios, or scenarios where a field needs to be customized for multiple times, there may still be situations where the customer-configured content becomes invalid, and repeated development and configuration are required, which affects the customer's product use. In order to solve the above problems, the following provides a detailed embodiment that can be optionally executed during the implementation of this solution. Please refer to Figure 3 , Figure 3 This is a flow chart of another field data processing disclosed in an embodiment of the present application. Another embodiment of the field data processing method of the present application includes:

[0057] 301. Create an initial standard table, and according to an update request of the initial standard data of the extended field and the standard field, update the initial standard data of the extended field and the initial standard data of the standard field in the initial standard table to the target standard data of the extended field and the target standard data of the standard field, so as to obtain a target standard table.

[0058] When processing field data, you can first create an initial standard table, and then based on the update request 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.

[0059] For example, see Figure 3-1 , Figure 3-1 A schematic diagram of an initial standard table disclosed in an embodiment of the present application, comprising Figure 3-1 It can be seen that "Extensible Field 1" and "Extensible Field 2" of the initial standard table are extended fields, "Field 1" and "Field 2" are standard fields, the initial standard data of "Extensible Field 1" is "FX='B'", the initial standard data of "Extensible 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 "Extensible Field 1" and "Field 1", the initial standard data of "Extensible Field 1" from "FX='B'" can be updated to "FX='B'and FY>100", and the initial standard data of "Field 1" from "abc" can be updated to "abcd" according to the upgrade request of "Extensible Field 1" and "Field 1".

[0060] It is worth mentioning that after the product is upgraded, only the initial standard data of the extended field is updated to the target standard data in the initial standard table, 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. Therefore, for the product upgrade scenario, the embodiment of the present application does not require repeated development and configuration, thereby reducing time and resource consumption, and will not affect the customer's product use. The customer's product experience is better.

[0061] 302. Create an initial extension table, and according to an update request of the initial extension data of the extension field, update the initial extension data of the extension field in the initial extension table to the target extension data of the extension field based on the updated extension data of the extension field, so as to obtain a target extension table.

[0062] An initial extension table may be created, and according to an update request for the initial extension data of the extension field, the initial extension data of the extension field in the initial extension table may be updated to target extension data of the extension field based on the updated extension data of the extension field to obtain a target extension table.

[0063] It is worth mentioning that when a certain field needs to be customized extended multiple times, only the initial extended data of the extended field is updated to the target extended data in the initial extended table, 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. Therefore, for the scenario where a certain field needs to be customized extended multiple times, the embodiment of the present application does not require repeated development and configuration, thereby reducing time and resource consumption, not affecting the customer's product use, and the customer's product experience is better.

[0064] Among them, based on the updated extended data of the extended field, the method of updating the initial extended data of the extended field in the initial extended table to the target extended data of the extended field can be 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 extension data of the extension field as the target extension data of the extension field" is a way of overwriting (replacing). For example, see Figure 3-2 , Figure 3-2 A schematic diagram of an initial extension table disclosed in an embodiment of the present application, comprising Figure 3-2 It can be seen that the initial extension data of "Extensible Field 1" of the initial extension table is "FX = 'B' And FXE = '2'", and the updated extension data "FX = 'B' And FXE = '1'" of "Extensible Field 1" can be used as the target extension data of the extension field to obtain the target extension table. "Combining the initial extension data of the extension field with the updated extension data of the extension field, and using the combined data as the target extension data of the extension field" is an appending method. For example, the initial extension data "FX = 'B' And FXE = '2'" of "Extensible Field 1" and the updated extension data "FX = 'B' And FXE = '1'" of "Extensible Field 1" can be combined, and the combined data can be used as the target extension data of "Extensible Field 1".

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

[0067] 303. After obtaining a 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, 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 is used as the target version data of the target field.

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

[0070] Steps 303 to 305 in this embodiment are similar to those in the previous Figure 2 Steps 202 to 204 in the illustrated embodiment are similar and will not be described in detail herein.

[0071] It is worth mentioning that in the existing field data processing method, if there is a need for the customer to obtain the data of the customized secondary development configuration of the field before, then after each upgrade, the same customized secondary development requirement needs to be repeatedly configured, and the efficiency of field configuration is low. In particular, when there are multiple upgrades, it is necessary to repeatedly configure the same customized secondary development requirement multiple times. Therefore, the efficiency of field configuration is particularly low, and the efficiency of field data processing is particularly low. In the present embodiment, if there is a need for the customer to obtain the data of the customized secondary development configuration of the field before, whether it is upgraded once or multiple times, the upgraded data and the customer's customized secondary development configuration data can be retained at the same time, and there is no need to repeatedly configure the same customized secondary development requirement. The efficiency of field configuration is high, especially when there are multiple upgrades, which can avoid the repeated configuration of the same customized secondary development requirement multiple times in the prior art. Therefore, the efficiency of field configuration in the present embodiment is high, and the efficiency of field data processing is high.

[0072] In this embodiment, an independent target standard table and a target extension table can be obtained, and the target standard table and the target extension table each contain standard data and extension data of the extension field, that is, multiple versions of the extension field can be retained at the same time, and the content configured by the customer will not be invalidated due to the new version update, and if the need to obtain the data configured before the field is to be met, the corresponding version data can be obtained from the target standard table or the target extension table in a targeted manner by determining whether the target field is an extension field, and there is no need to redevelop and configure the same configuration requirements, which reduces repeated development and configuration work, reduces time and resource consumption, does not affect the customer's product use, and the customer's product use experience is better. Secondly, when the product is upgraded, only the initial standard data of the extension field in the initial standard table is updated to the target standard data, and the extension data of the extension field of the extension table is not modified, and the extension data of the extension field is still retained, and there is no need to repeat the development and configuration, therefore, time and resource consumption is reduced, and the customer's product use is not affected, and the customer's product use experience is better. Next, when a certain field needs to be customized for multiple extensions, only the initial extension data of the extension field is updated to the target extension data in the initial extension table, and the standard data of the extension field in the standard table is not modified. The standard data of the extension field is still retained. Therefore, there is no need to repeat the development configuration, thereby reducing time and resource consumption, and will not affect the customer's product use, and the customer's product experience is better. Furthermore, the method of overwriting / appending extension data can provide the diversity and feasibility of updating the extension data of the extension field in the initial extension table, and improve the diversity of the extension version data, the diversity of the version data that users can obtain, and the user experience. Finally, if there is a need for the customer to obtain the data of the customized secondary development configuration before the field, whether it is upgraded once or multiple times, the upgraded data and the customer's customized secondary development configuration data can be retained at the same time, and there is no need to repeat the configuration of the same customized secondary development requirements. The efficiency of field configuration is high and the efficiency of field data processing is high.

[0073] based on Figure 2 In the described embodiment, during the process of field data processing, although multiple versions of extended field data can be retained through independent target standard tables and target extended tables, the customer-configured content will not become invalid due to new version updates, and the corresponding version data can be provided, which reduces repeated development and configuration work, reduces time and resource consumption, and improves the customer's product experience to a certain extent. However, there may be a situation where the returned version data does not match the required version data, resulting in an inaccurate return of the field data version. In order to solve the above problem, the following provides a detailed embodiment that can be optionally executed during the implementation of this solution. Please refer to Figure 4 , Figure 4 This is a flow chart of another field data processing disclosed in an embodiment of the present application. Another embodiment of the field data processing method of the present application includes:

[0074] 401. Obtain a target standard table and a target extension table, wherein the target standard table includes target standard data of an extension field and target standard data of a standard field, and the target extension table includes target extension data of an extension field.

[0075] 402. After obtaining a 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 similar to those in the previous embodiment. Figure 2 Steps 201 to 202 in the illustrated embodiment are similar and will not be described in detail herein.

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

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

[0079] Among them, if the target extension table includes target extension data for extending the target field N times, 1≤N, and the target version data is the nth extension data of the nth extension of the target field, 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 can be understood that the Nth extension data of the Nth extension is the latest version data, and the larger n is, the newer the version corresponding to the nth extension data is. Specifically, for example, if the target field is "Extensible Field 1", and the target extension table includes target extension data for three extensions of "Extensible Field 1", the target extension data includes the first extension data "FX='B'And FXE='2'" of the first extension, the second extension data "FX='B'And FXE='3'" of the second extension, and the third extension data "FX='B'And FXE='1'" of the third extension, if the target version data is the Nth extension data of the Nth extension of "Extensible Field 1", then the Nth extension data (latest version data) of "Extensible Field 1" in the target extension table can be used as the target version data of "Extensible Field 1".

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

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

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

[0084] In this embodiment, an independent target standard table and a target extension table can be obtained, and the target standard table and the target extension table each contain standard data and extended data of the extension field, that is, multiple versions of the extension field can be retained at the same time, and the content configured by the customer will not be invalidated due to the new version update, and if the need to obtain the data configured before the field is to be met, the corresponding version data can be obtained from the target standard table or the target extension table in a targeted manner by determining whether the target field is an extension field, and there is no need to redevelop and configure the same configuration requirements, which reduces repeated development and configuration work, reduces time and resource consumption, does not affect the customer's product use, and the customer's product use experience is better. Secondly, for the extension field, if the standard version data is required, the standard version data is returned, if the extended version data is required, the extended version data is returned, and if the nth extended version data is required, the nth extended version data is returned, that is, the version data corresponding to the required target version data can be returned, and the accuracy of the field data version returned is relatively high.

[0085] based on Figure 2 , Figure 3 and Figure 4 On this basis, in order to improve the accuracy and efficiency of determining whether the target field is an extension field, this can be achieved by setting and utilizing the extension identifier of the extension field. For specific implementation methods, please refer to the following description:

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

[0087] Specifically, for easier understanding of the embodiments of this application, please refer to Figure 5 , Figure 5 A flowchart of another field data processing method disclosed in an embodiment of the present application is shown in FIG. Figure 5 It can be seen that the field data processing process includes two stages: design time and runtime:

[0088] 1. Design stage: For each extension field, add the "Extensible" property option to set the extension flag of the extension field;

[0089] 2. Runtime phase:

[0090] (1) Data reading stage: For an extended field with an extended identifier, the corresponding extended field can be found from 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 the extended fields with extended identifiers, the front-end (client) can provide an extended modification operation button on the right side of the extended field control. When the modification is enabled, click the button to modify the field content in the pop-up interface. The modification supports overwriting and appending. Appending means adding a new extended row and increasing the maximum version number by 1. However, the data of the standard original version (the standard data of the extended field in the standard table) cannot be overwritten.

[0092] (3) Data preservation stage: For the extension field with the extension flag set, determine whether the extension field exists in the extension table. If not, create the extension field and then save the field content according to the content set in the "data modification stage".

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

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

[0095] The above describes the field data processing method in the embodiment of the present application. The following describes the field data processing device in the embodiment of the present application. Figure 6 , an embodiment of the field data processing device in the embodiment of the present application includes:

[0096] an acquisition unit, configured to acquire a target standard table and a target extension table, wherein the target standard table includes target standard data of an extension field and target standard data of a standard field, and the target extension table includes target extension data of the extension field;

[0097] a determination unit, configured to determine whether the target field is an extended field after obtaining a read request for target version data of the target field;

[0098] The determining unit is further configured to use, if the target field is an extension field, 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;

[0099] The determining unit is further configured to use the target standard data of the target field in the target standard table as the target version data of the target field if the target field is a standard 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 an update request 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 a target standard table.

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

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

[0103] The determination unit is specifically used 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; 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 determination unit is specifically used to use the nth extension data of the target field in the target extension table as the target version data of the target field, the target extension table includes target extension data for extending the target field N times, 1≤N, and the target version data is the nth extension data of the nth extension of the target field, 1≤n≤N.

[0105] The field data processing device also includes:

[0106] A setting unit, used to set an extension identifier of the extension field;

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

[0108] In an embodiment of the present application, independent target standard tables and target extension tables can be obtained, and the target standard tables and target extension tables each contain standard data and extended data of the extension field, that is, multiple versions of data of the extension field can be retained at the same time, and the customer-configured content will not become invalid due to the new version update. In addition, if the need to obtain the data previously configured for the field is to be met, the corresponding version data can be obtained from the target standard table or the target extension table in a targeted manner by determining whether the target field is an extension field. There is no need to redevelop and configure the same configuration requirements, which reduces repeated development and configuration work, reduces time and resource consumption, does not affect the customer's product use, and the customer's product use experience is better.

[0109] See below Figure 7 In the embodiment of the present application, an embodiment of the computer device 700 includes:

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

[0111] The memory 705 is a temporary storage memory or a permanent storage memory;

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

[0113] The embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium includes instructions, when the instructions are executed on a computer, the computer executes the aforementioned Figure 2 , Figure 3 and Figure 4 The method in the illustrated embodiment.

[0114] The present application also provides a computer program product including instructions, which, when executed on a computer, enables the computer to execute the aforementioned Figure 2 , Figure 3 and Figure 4 The method in the illustrated embodiment.

[0115] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

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

[0117] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

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

[0119] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0120] If the integrated unit is implemented in the form of 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 the present application is essentially 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, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.

Claims

1. A field data processing method, characterized in that: include: Acquire a target standard table and a target extension table, wherein the target standard table includes target standard data of an extension field and target standard data of a standard field, and the target extension table includes target extension data of the extension field; After obtaining a read request for the target version data of the target field, determining whether the target field is an extended field; If the target field is an extended field, 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 are used as the target version data of the target field; If the target field is a standard field, the target standard data of the target field in the target standard table is used as the target version data of the target field.

2. The method according to claim 1, characterized in that The target standard table is obtained, including: Creating an initial standard table, the initial standard table including initial standard data of the extended field and initial standard data of the standard field; According to 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 obtaining target extension table includes: Creating an initial extension table, wherein the initial extension table includes initial extension data of the extension field; According to an update request of the initial extension data of the extension field, based on the update extension data of the extension field, the initial extension data of the extension field in the initial extension table is updated to the target extension data of the extension field to obtain a target extension table.

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

5. The method according to any one of claims 1 to 4, characterized in that: The 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, the target standard data of the target field in the target standard table is used as the target version data of the target field; If the target version data is extended version data, 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 for extending the target field N times, 1≤N, and the target version data is the nth extension data for the nth extension of the target field, 1≤n≤N; The using the target extension data of the target field in the target extension table as the target version data of the target field comprises: The nth extension data of the target field in the target extension 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 extension table, the method further includes: Setting an extension identifier of the extension field; The determining whether the target field is an extension field comprises: Based on the extension identifier of the target field, it is determined whether the target field is an extension field.

8. A field data processing device, characterized in that: include: an acquisition unit, configured to acquire a target standard table and a target extension table, wherein the target standard table includes target standard data of an extension field and target standard data of a standard field, and the target extension table includes target extension data of the extension field; a determination unit, configured to determine whether the target field is an extended field after obtaining a read request for target version data of the target field; The determining unit is further configured to use, if the target field is an extension field, 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; The determining unit is further configured to use the target standard data of the target field in the target standard table as the target version data of the target field if the target field is a standard field.

9. A computer device, characterized in that: include: CPU and memory; The memory is 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 comprises instructions, and when the instructions are executed on a computer, the computer is caused to perform the method according to 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, the computer is caused to execute the method according to any one of claims 1 to 7.

Images