Baucore

Barbour ABI

Conceptuseradmin

Barbour ABI is a UK construction-industry intelligence platform, and is Baucore’s UK-market counterpart to the ibau integration for Germany — same underlying provider architecture (Prov_Search__c, Prov_Field_Mapping__c, Prov_Picklist_Mapping__c, described in External Data Providers), pointed at a different regional data source. This page is the overview; setup is in Barbour ABI Setup, and licensing/subscription detail is in Barbour ABI Subscription.

What you get

  • Search Barbour ABI’s project database from a dedicated app page, with the same address/city/street/ID-based search pattern as ibau.
  • A map view on search results, with project detail shown on click.
  • Projects related to an Account surface directly on that Account’s or Lead’s Lightning record page — the same “IBAU/BarbourABI” record-page tile serves both providers.
  • A dedicated abiProject component renders Barbour ABI project detail (participants, address, measures) wherever a matched project is displayed.

Sync and identifiers

  • Each synced project and participant carries a barbourABI_ID__c external ID, parallel to the IBAU_ID__c field used for ibau — both live on Project, Project Lead, and Participant records so the two providers can coexist without clashing.
  • Sync jobs run on a dedicated scheduler (abi_Sync_Scheduler), separate from the ibau scheduler, driven by saved search profiles (Prov_Search__c) with Provider__c set to the Barbour ABI value.
  • As with ibau, participant role mapping determines whether a synced participant is created automatically or held for the user to map a role first.

Credentials

Barbour ABI authentication is stored per user in External Project Credential records, validated against the provider API on save — the same credential model used for ibau. Only one active credential should exist per user per provider; deactivate an old one before activating a replacement.

Barbour ABI does not currently have a dedicated developer technical reference the way ibau does — if you hit provider-specific behavior not covered here (field mapping edge cases, sync frequency limits), treat the ibau documentation as the closest analog and confirm against your org’s actual Barbour ABI configuration, since some details may differ between the two providers.

Still need help?

Our support team is happy to help with anything not covered here.

Contact support