Advanced Push: Send pre-filled forms with table to your field workers!
This tutorial is based on the “Push” tutorial. If you do not know what the push is, we recommend you to consult our tutorial: Send pre-filled forms to the field workers.
Generally for a transfer, only fields outside a table can be filled via a push. But it is now possible to pre-filled tables using Excel sheets. For the same push, it is also possible to send only some lines of a table.
The push allows you to send your pre-filled forms from the office to the mobiles of your field workers. In this tutorial, we explain how to pre-filled table of your Push through Excel import.
Here you will define your import model, in correlation with the Excel file that you will create in the second stage.
Note: The first field is ‘Recipient‘. The recipient corresponds to the user identifier (User ID).
A first approach for sending a table would be to make as many imports as recipients; this approach is tedious and limited. But do not worry! Kizeo brings you a solution! You can send multiple ‘push’ with tables via a single import.
There are 2 important notions to remember for the creation of the excel file:
The goal here is to be able to link the rows to be pre-filled with the push.
The rows of tables to be pre-filled can be the same for all pushes; in this case there is a push-id equal to 1 and a push_parent_id which is also equal to 1.
The rows of tables to be pre-filled can be different according to the push. Depending on the user ,for example, we could want to push a different information. In this case, the push intended for a user and the rows of tables destined for him will have the same identifiers.
The easiest case would be sending all the contents of a table to users. We want to send 5 push to 3 different users: Amah, Baculard and Zanotti. Our form contains two tables: Articles and Inventories.
To create this push, you only need to assign the same identifier to each user concerned (PUSH_ID = 1) and to each row of the table (PUSH_PARENT_ID = 1) as illustrated in the following picture.
In this case users will receive the same contents for the “articles” and “inventories” tables.
In this case, you simply need to distinguish between identifiers of the push to filter the rows of the tables.
Example: We want to send 5 push to 3 different users: Amah, Baculard and Zanotti. Our form contains two tables: Articles and Inventories.
In this example, pushes A, B, C, D and E will only send the rows of the table which PARENT_ID correspond to their PUSH_ID.
For the push B (with identifier 2), the user “amah” will receive an empty table “articles” because no row in this table has a PUSH_PARENT_ID corresponding to the identifier 2. Contrary to the push D, user Zanotti (PUSH_ID = 4) will receive a table “articles” with a completed row (PUSH_PARENT_ID = 4) and another row in the “Inventories” table (PUSH_PARENT_ID = 4).
Do not hesitate to comment on this artile!
All your questions, comments and suggestions are most welcome!