In Geovonic Connect, data sources provide connectivity to third-party business systems. The Brightly Assetic data source allows you to fetch real-time data from your asset management system using the Assetic ODATA API.

For example, the Assetic data source allows you to configure searches to retrieve asset or document information from Assetic. This article assumes that you have some knowledge of using Assetic queries to fetch data.

Data Source Configuration

The Assetic data source configuration requires a few fields: –

• Assetic Service Domain – the host name of your Assetic server.
  For example, lionsheadcouncil.assetic.net
• Credentials – a username and password for an Assetic user.

It is important when configuring any integration service to follow the Principle of Least Privilege. Any credentials used for the data source should only be able to access the minimum amount of information to meet the needs of your Geovonic Connect application. For example, do not provide the admin credentials for your Assetic server if Geovonic Connect only needs to access limited records. Best practice is to create a new user with the least required privileges.

Layer Link Configuration

The Assetic layer link configuration uses the Assetic ODATA API and requires several fields: –

• Entity Type – Select from the list of entities (e.g. assets or documents).
• Filter – An ODATA filter statement to fetch related records.
  For example, ComplexAssetId eq '{{ASSETIC_ID}}' would return records where the Assetic ComplexAssetId field matches the map feature using the asseticid attribute.
• Select – The list of field names to be returned.
  For example, Id,ComplexAssetId,ComplexAssetAssetCategory,ComplexAssetName. The full list of field names can be found using your Assetic ODATA schema at https://<your-server>.assetic.net/odata/$metadata.
• Top – The maximum number of results to be returned.
• Order – The sort order for the returned results. For example, ComplexAssetName asc
• Test data – Include example values for any field attributes that will be used when validating this layer link.
  For example, {{ASSETIC_ID}}=AB1235C

Where queries are potentially returning multiple records for a single map feature, be sure to include a Top value  to set the maximum number of records that should be returned. This prevents very large datasets being inadvertently returned to the user’s browser.