Setting up the Lens Integration (Imagery and Notes)

There are two Lens Integrations available to use within Landscape: The Lens Notes integration and the Lens Imagery integration. Both integrations require the same setup.

If you haven't set up your Lens account yet, you can export a shapefile of all of the boundaries you wish to import into Lens by using Data Viewer (see the callout section below on how to do this). This export can include the fields 'src_id' (which enables you to link the Property to Landscape) and 'Record Name' (which allows you to name the property in Lens), as well as any other Portfolio Record fields you'd like to include. Share this shapefile with the Lens team when you're setting up your account and tell them you'd like it to be integrated with Landscape.

If you already have Lens and wish to integrate with your Landscape account, then you'll need to request a shapefile export from the Lens team, and fill in the field that they specify with the Landscape ID for each record in your Lens account. You can use Views to easily see all of the ID numbers of all of the IDs in your Landscape account.

Once these steps are complete, the Lens team will provide you with an API key.

Next, head to Settings > Integrations (you must be an Administrator to access Settings) and find the 'Upstream Tech' section. Click 'Enable' and enter the API key that they provided to you.

You can click on the Integrations Settings button to confirm that 'src_Id' is the field that is being used for the synchronization, and you'll probably want to make sure that 'Automatically create new Issues from Lens notes' is unchecked (this is for special legacy users of the integration and should not apply to new integrations).

How the 'src_Id' field is used to maintain and troubleshoot the integration. Whenever you export one or multiple boundary shapefiles from Landscape, it will always contain the field 'src_Id'. 'src_Id' is a string of digits and numbers that is unique to that record in Landscape. When you then import the shapefile into Lens, Lens will see the 'src_Id' field and know which record to place the data into in Landscape. Most issues with record synchronization are tied to this field either not being present in the Lens shapefile, or being incorrect. The solution is then to re-export the boundary from Landscape and re-import it into Lens.



Maintaining the Integration

Integration settings can be found in Settings > Integrations in the 'Upstream Tech' section. From here you can force a sync and access the integration settings. From settings you can see the Landscape record id field name (see above callout for more information). You probably want to keep this field as the default 'src_Id' since this field is automatically included in all exported record boundary shapefiles and is designed to work with this integration. There is also an option for 'Automatically create new issues from Lens notes' which should be left unchecked. This is an option specifically for legacy users of the integration.

Adding new records to Lens

To add a new synchronized record to Lens, simply export the boundary from Landscape and then import it into Lens when you create the new property there. The exported Landscape boundary should already contain the 'Src_id' field and not require any editing. If the property has already been created in Lens, then you'll just need to re-upload the old shapefile with the new one from Landscape by following these instructions.

Once the boundary is uploaded the integration should begin working as soon as the next sync.

To export a single record boundary, navigate to the record and click on the boundary on the map, then click on the 'export' button and select the shapefile option. You can also use the export button on the map toolbar, but the exported file must be the boundary file (not a 'Property Area', 'General Area' or 'Property Line' etc.)



Exporting multiple record boundaries at once using Data Viewer

This short video explains how to quickly generate a shapefile of multiple records at once using Data Viewer


Still need help? Contact Us Contact Us