While computed fields can help transform your data within a Collection into a more useful state, you may also need to connect data across Collections. To accomplish this, you would use join fields. Join fields are akin to a vlookup table in Excel, only more powerful.
Join fields can help you relate a claims form to customer policy data, ties purchase orders to customer records from your CRM or connect invoices to a vendor database, to an accounts payable system (or both), and much more.
In Impira, you can make these connections easily, right in the UI, without the need to engage in an IT project. Joining data from various Collections on fields they have in common can provide you with a more holistic view of your business.
Example: Joining two collections
As an example, let’s look at joining data from two Collections. For this example, you have a Collection called IX920 from which Impira has extracted a few fields:
You’ve also opened a CSV file as data, which creates a new Collection:
Note that both the IX920 and CRM_Data.csv Collections contain the account number (the names of the fields need not match -- one might have been “Account No.” and the other “Account.” You can use that common data to create a Join field, as follows:
First name the new field, and select a field in the current Collection to use for the Join,
in the example, we’ll use ‘Account Number’:
Then, select the other Collection, and from the dropdown that appears, choose the field in the other collection with the same values;
in this example, it’s also called ‘Account Number’
Your collection now looks like this, with a new ‘Account’ value populated for any record with matching Account Numbers in your two Collections:
So where our CSV file only provided the Birst City and State and License Number for each account, by using the Join function, we can see the Name, Amount and any other informations that was extracted from the IX920 forms: