Accounting Integration: FOUNDATION Requirements & Instructions

This resource will give important requirements for this integration, as well as instructions for implementing the integration, field mapping, etc.

đź’ĄIntegrations is a premium product and requires a separate license. Please contact your Account Manager for more information on premium product licenses or reach out to Customer Support at [email protected] or call 888.836.6269.

Integration Setup Instructions

1

Customer provides information related to the server and how to access it from the internet.

  • If the server is hosted, Tenna will need:
    • Server name (i.e., sql.FOUNDATIONsoft.com)
    • Port
    • Username (to be provided by customer)
    • Password (to be provided by customer)
    • Database name
    • Encrypted true or false
  • If the server is on-prem, the customer will need to provide a tunnel into the server for read-only access.
    • Server name
  • The server needs to be exposed to the internet and access granted to Tenna.
    • Username (to be provided by customer)
    • Password (to be provided by customer)
    • Database name
    • Encrypted true or false
  • There are two modules Tenna can connect to and pull information:
    • Equipment (known as assets in Tenna)
    • Jobs (known as sites in Tenna)

NOTE: Customer can choose to pull one or both of these.

2

Customer will need to setup a new category in Tenna as one of the following.

  • “New from FOUNDATION” (case sensitive) with type Equipment.
    • Navigate to settings, categories
    • Click + on Major Category column
    • Add “New from FOUNDATION”
    • Select Equipment as Category Type
    • Select an icon to be used
  • When equipment is added or updated in FOUNDATION, the integration will search Tenna Asset Fleet Number to match FOUNDATION Equipment Number.
    • When no match is found, a new Asset will be created in Tenna and the fields will be populated according to the table below (<)
    • If there is a match, the corresponding fields will be updated according to the table below (<<)
  • When a job is added or updated in FOUNDATION, the integration will search Tenna Site Name to match FOUNDATION Job Description.
    • When no match is found, a new Site will be created in Tenna and the fields will be populated according to the table below (<)
    • If there is a match, the corresponding fields will be updated according to the table below (<<)

Important!

  • Any information already in Tenna, will be changed to what comes from FOUNDATION. Including address changes.
  • Do not remove any assets with a tracker from Tenna.
  • FOUNDATION has no API capabilities, so there is no Tenna to FOUNDATION synchronization. The meter readings can be fed manually in FOUNDATION by utilizing the import function in FOUNDATION.
  • Multiple FOUNDATION databases feeding into one Tenna instance is not currently supported.

Field Mapping

FOUNDATION Jobs to Tenna Sites

Filters

None

Sync Frequency

Every 1 hour

Data Mapping

Customized Fields

  • name: Foundation does not have a concept of “names” but instead uses Job Number, Company Number, and Description to find items. As such we have combined Company Number and Job Number to hopefully create a unique name for the site within Tenna.
  • type: Foundation has no concept of job types. As such we default to “project”.
  • country: We use a provided “job_country” but default to the United States. If the site is within the United States in Foundation then the “job_country” field will be null.

Job Validation SQL

  • SELECT TOP 1 description , job_id, company_id, job_start_date, job_status, original_cost, est_completion_date, address_1,address_2 , city, state,job_country , zip_code from jobs
  • (Run this SQL Query in the Foundation database to validate the required data columns exists and are populated prior to activation)

FOUNDATION Equipment to Tenna Assets

Filters

None

Sync Frequency

Every 1 hour

Data Mapping

Customized Fields

  • category_id: This is configured to be the “New from Foundation” category by default with type of equipment. Foundation has categories, but Tenna does not pull the foundation category to allow you to maximize flexibility within Tenna. Tenna can do a bulk upload of categories per asset to match how you decide you want them set.

Equipment Validation SQL

  • SELECT TOP 1 equipment_no , description , manufacturer , make_model , model_year, serial_number , license_plate_no , purchase_date , purchase_price ,sale_date , sale_price from equipment
  • (Run this SQL Query in the Foundation database to validate the required data columns exists and are populated prior to activation)

Expected Implementation Timeline

NOTE: For questions, reach out to the Tenna Integrations Department [email protected].

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.