Still need help?
This article explains the Get Data from Other App block that can be used to design an app.
Click on the block and start editing on the panel that appears on the right side.
This is what appears as the label for the dropdown that shows the list of the items from the master app. Usually people provide labels like "Select the customer/project/item".
Next step is to select the app from which the data will be fetched. You should get a dropdown of all the apps that are there in your Workplace. If you don't see anything then probably this is your first app. In such a case, you should create a master app first.
Once you select your Data source app, additional fields will appear on the right panel for you to configure.
These are the fields that you need to show to the end users so that they can identify the item to be selected. For example, the app designer is setting Customer's Id and Customer's Name as selection field.
As an example, if there are the following entries in Customer Master -
Now while making a submission, if the user types "CLAP50", the first two entries will match the search text. If the user types "CLAP505", only the first entry will show up.
.png)
Here you select the items that will be pulled against the main selection made by the user. For example, if the user selects a Customer from the dropdown, all the details selected below will be fetched against that customer.
Make this field editable
You can edit the values of the pulled fields. Normally once you fetch data, all fields are automatically filled. To allow users to make edits to specific pulled fields, each field can be individually configured to be made editable.
Enable this option if you want the pulled field to be hidden to the users while they use the app.
This option appears once ‘Hidden’ is enabled for the pulled field. Keep this setting enabled if you want the field's value to be retained even when the field is hidden. This is useful for preserving user input in cases where the field may temporarily disappear based on conditions.
Clappia allows admins to set status for each submission. It can be configured in the app designer configuration tab. You can set the status of each item in the master app and then fetch only those items that have a particular status. For example, you can set the statuses as Active/Inactive customer or Available/Unavailable (for inventory master).
This is optional and you should configure the status in the master app first to configure this.
The fetched data that shows while the user types in to search can be sorted according to the fields from the Master app.
Once you click on Add column, select the field the data is to be sorted by. There can be multiple columns added.
Using the above example; the fetched data is sorted by status in the Master app (inactive customer, active customer).
.png)
Enable this option to tell the user that it is a compulsory field.
Enable this option to allow the users to be able to pull all the fields from the source app. If not, only the fields that have permission will be allowed to pull.
Example: Say there are 2 apps, App1 being the Master app and App2 is where you use the Get Data from other Apps block to fetch data from App1. If a user has access to only App2 and not App1, then by keeping the ‘Allow users to see all records in the source app’ option enabled in App2 in the Get Data from other Apps block, users will be able to search records from the master app even though they do not have access to that app. This ensures that they are able to use certain information from the Master app only and not have direct access to that app.
A custom message to show to the admin that there are no submissions found from the data the user types in to search.
The minimum number of characters the user should enter in the field to pull up the search list.
Give the maximum number of search results to be displayed in the dropdown after a user enters into the field.
Use this option if you want to show or hide a field under certain conditions. It accepts the standard Clappia Formulae, similar to conditional sections.
Enable this to allow the field value to be changed after submission
Example: Pulling information from a ‘Leads’ App to another app called ‘Updates’ App.
App1 - Leads App
App 2 - Updates App
The Get data from other Apps is configured as the following:
Label: Get data from Leads App
Data Source App: Leads
Selection Fields: ID
Pulled fields: Customer Name, Customer Email, Phone Number, Stage
As the pulled fields are a copyable section from the 1st app, the fields will show up as a separate section.
In the pulled section, you can add additional fields to capture data apart from the pulled fields.
The added fields will be replicated in every copied section in App Home when data is pulled from the 1st app.
This is a feature in GET DATA from other apps which is used to filter the fields and pull the data according to specific requirements.
Click on this option to add a dynamic filter. It opens up a menu to select the filtering items.
Let us understand the working of dynamic filter more clearly with an example
Dynamic filtering will help to view only those tickets that are assigned to the support employee. One employee can view, access or change the status of the tickets which are assigned to them and not of others.
There are 2 apps:
This is a list of tickets assigned to employees in the Assigning Tickets app.
Consider an employee ID and the tickets assigned only for that employee.
Employee ID - CLP0008
Ticket Number - sup_clp14 and sup_clp3
Now, check the status of tickets in the Status Update on Tickets app.
When you type the employee name, the respective employee details are fetched.
Next when you want to select tickets assigned to that employee it shows the list of all tickets.
This is where the Dynamic Filter is useful.
Edit the app and click on the Ticket Number block which is the ‘Get Data from Other Apps’ block.
Assigning Tickets is the app selected to pull fields from.
Employee ID is selected - this implies that ticket numbers assigned to the employee ID will be displayed.
Status update on tickets is the current app.
Employee ID is selected - this implies that the employee ID of the current app will match the employee ID of the app from which the data is pulled from. In this example it is the Assigning Tickets app.
Click on save and now let’s search for the tickets assigned to the employee again.
Due to the dynamic filter that was added, now only the tickets which are assigned to that particular employee will be shown.
140L, 5th Main Rd, Sector 6, HSR Layout, Bengaluru, Karnataka 560102, India
+91 96418 61031
3500 S DuPont Hwy, Dover,
Kent 19901, Delaware, USA
+1 (341) 209-1116
.svg){kind=small}
3500 S DuPont Hwy, Dover,
Kent 19901, Delaware, USA
+1 (341) 209-1116
140L, 5th Main Rd, Sector 6, HSR Layout, Bengaluru, Karnataka 560102, India
+91 96418 61031