System and method for bulk update of resource data for view parameters

1. A system for bulk updating resource data of parameters included in a view, the system comprising:

at least one memory storing instructions; and

at least one processor configured to execute the instructions to:

receive a user request to bulk import data of the parameters for a plurality of instances of the view, the received user request including a file comprising rows of the data, each row corresponding to a different instance of the view;

based on the received user request, make, by a first application, an import data application programming interface (API) call to bulk import the data into one or more tables to which the data of the parameters is to be saved;

based on the import data API call, make a save data API call to update existing resource data of the parameters, stored in the one or more tables, with the data included in the file; and

based on the save data API call, update, in the one or more tables, the existing resource data of the parameters for the plurality of instances with the data included in the file,

wherein the import data API and the save data API are generic across a plurality of views and a plurality of tables.

2. The system as claimed in claim 1 , wherein the file further comprises:

a row of column headers with identifiers of the parameters included in respective columns of each of the rows of data; and

metadata including the identification information of the parameters, validation information for each parameter, and table information indicating the one or more tables for which resource data of the parameters is stored.

3. The system as claimed in claim 2 , wherein the at least one processor is further configured to execute the instructions to, based on the import data API call, validate the row of column headers with the metadata by confirming that identifiers of the parameters included in the row of column headers correspond to the identification information of the parameters.

4. The system as claimed in claim 2 , wherein the at least one processor is further configured to execute the instructions to:

for each of the data in a row, perform a validation by comparing the data to the validation information; and

make the save data API call for a row based on the validation being performed successfully.

5. The system as claimed in claim 1 , wherein:

the save data API call is made separately for each of the rows of the data; and

an input to the save data API comprises identifiers of the one or more tables, identifiers of the parameters, and data included in a corresponding row for which the save data APIis called.

6. The system as claimed in claim 5 , wherein the at least one processor is further configured to execute the instructions to:

obtain information of a second application;

send, based on the obtained information of the second application, a request to the second application to store first data, from among the data, of at least one first parameter, from among the parameters, to at least one table associated with the second application, from among the one or more tables; and

store, by the second application, the first data to the at least one table.

7. The system as claimed in claim 5 , wherein:

the at least one processor is further configured to execute the instructions to obtain identifiers of one or more primary keys corresponding to the view; and

the input to the save data API further comprises the identifiers of the one or more primary keys, and one or more primary key values corresponding to the instance of the view.

8. The system as claimed in claim 7 , wherein the at least one processor is further configured to execute the instructions to, for each of the at least one table, search for an existing data object or record corresponding to a primary key value of the one or more primary key values.

9. The system as claimed in claim 1 , the at least one processor is further configured to execute the instructions to:

generate a response file indicating, for each of the rows of the data, whether the updating is successfully; and

return, by the import data API, the generated response file for output to a user.

10. A method, performed by at least one processor, for bulk updating resource data of parameters included in a view, the method comprising:

receiving a user request to bulk import data of the parameters for a plurality of instances of the view, the received user request including a file comprising rows of the data, each row corresponding to a different instance of the view;

based on the received user request, making, by a first application, an import data application programming interface (API) call to bulk import the data into one or more tables to which the data of the parameters is to be saved;

based on the import data API call, making a save data API call to update existing resource data of the parameters, stored in the one or more tables, with the data included in the file; and

based on the save data API call, updating, in the one or more tables, the existing resource data of the parameters for the plurality of instances with the data included in the file,

wherein the import data API and the save data API are generic across a plurality of views and a plurality of tables.

11. The method as claimed in claim 10 , wherein the file further comprises:

a row of column headers with identifiers of the parameters included in respective columns of each of the rows of data; and

metadata including the identification information of the parameters, validation information for each parameter, and table information indicating the one or more tables for which resource data of the parameters is stored.

12. The method as claimed in claim 11 , further comprising, based on the import data API call, validating the row of column headers with the metadata by confirming that identifiers of the parameters included in the row of column headers correspond to the identification information of the parameters.

13. The method as claimed in claim 11 , wherein the making the save data API call comprises:

for each of the data in a row, performing a validation by comparing the data to the validation information; and

making the save data API call for a row based on the validation being performed successfully.

14. The method as claimed in claim 10 , wherein:

the save data API call is made separately for each of the rows of the data; and

an input to the save data API comprises identifiers of the one or more tables, identifiers of the parameters, and data included in a corresponding row for which the save data API is called.

15. The method as claimed in claim 14 , wherein the updating the existing resource data comprises:

obtaining information of a second application;

sending, based on the obtained information of the second application, a request to the second application to store first data, from among the data, of at least one first parameter, from among the parameters, to at least one table associated with the second application, from among the one or more tables; and

storing, by the second application, the first data to the at least one table.

16. The method as claimed in claim 14 , wherein:

the making the save data API call comprises obtaining identifiers of one or more primary keys corresponding to the view; and

the input to the save data API further comprises the identifiers of the one or more primary keys, and one or more primary key values corresponding to the instance of the view.

17. The method as claimed in claim 16 , wherein the updating the existing resource data comprises, for each of the at least one table, searching for an existing data object or record corresponding to a primary key value of the one or more primary key values.

18. The method as claimed in claim 10 , further comprising:

generating a response file indicating, for each of the rows of the data, whether the updating is successfully; and

returning, by the import data API, the generated response file for output to a user.

19. A non-transitory computer-readable recording medium having recorded thereon instructions executable by at least one processor to perform a method for bulk updating resource data of parameters included in a view, the method comprising:

receiving a user request to bulk import data of the parameters for a plurality of instances of the view, the received user request including a file comprising rows of the data, each row corresponding to a different instance of the view;

based on the received user request, making, by a first application, an import data application programming interface (API) call to bulk import the data into one or more tables to which the data of the parameters is to be saved;

based on the import data API call, making a save data API call to update existing resource data of the parameters, stored in the one or more tables, with the data included in the file; and

based on the save data API call, updating, in the one or more tables, the existing resource data of the parameters for the plurality of instances with the data included in the file,

wherein the import data API and the save data API are generic across a plurality of views and a plurality of tables.