Skip to main content

Data Connections

Report Forge can pull reporting data from multiple source systems. The data connection defines where the data comes from, how it is authenticated, and how often it refreshes. Each blueprint's sections are mapped to a data connection to supply the fields contributors and outputs use.

Data connections overview

Supported connectors​

ConnectorDescriptionAuthentication
OptiPlan (Kazinex)Native connector to the Kazinex OptiPlan scheduling module. Provides schedule, resource, cost, and earned value data.Authenticated via the Kazinex session \u2014 no separate credentials required.
SQL ServerDirect connection to an on-premises or Azure SQL Server database. Queries return rows mapped to blueprint sections.SQL Server authentication or Windows/Azure AD authentication.
Excel / CSVConnect to a static or dynamic Excel file or CSV stored in SharePoint, OneDrive, or uploaded directly.SharePoint/OneDrive OAuth or file upload.
SharePoint ListRead list items from a SharePoint Online list as report data rows.Microsoft 365 OAuth (user or service principal).
OData feedConnect to any OData v4 REST endpoint.Bearer token, API key, or anonymous.
REST APIConnect to a custom JSON REST API. Requires a field mapping configuration.Bearer token or API key.

Adding a data connection to a blueprint​

  1. Open the blueprint in the Blueprint Designer.
  2. Click Data → Manage connections.
  3. Click + New connection.
  4. Select the Connector type.
  5. Configure the connector-specific settings (see below).
  6. Click Test connection to validate.
  7. Click Save.

Connector-specific setup​

OptiPlan (Kazinex)​

No connection setup is required. The connector automatically resolves the project schedule data for the active project. In the section field mapping, select which OptiPlan data domain to expose:

  • Activity / Schedule data
  • Resource assignments
  • Cost accounts
  • Earned value metrics
  • Risk register
  • Milestones

SQL Server​

FieldDescription
ServerHostname or IP address of the SQL Server instance.
DatabaseThe database name.
AuthenticationSQL Server auth (username/password) or Azure AD.
QueryThe SELECT statement returning the rows for this section. Use {ParameterName} placeholders for runtime-filtered queries.
Query timeoutMaximum seconds to wait for the query to complete (default: 30s).
Refresh modeOn demand (manual refresh), On edition open, or Scheduled.

Security note: Use a read-only SQL user for all Report Forge connections. Report Forge never writes to connected databases.

Excel / CSV​

FieldDescription
SourceUpload a file directly, or link to a SharePoint/OneDrive URL.
Sheet / rangeFor Excel: the sheet name and optional named range.
Header rowWhether the first row contains column headers.
Date formatThe date format used in the file (for correct date parsing).
Refresh modeOn demand or scheduled. For linked files, Report Forge re-reads the file on refresh.

SharePoint List​

FieldDescription
Site URLThe SharePoint site containing the list.
List nameThe display name of the SharePoint list.
Field mappingMap SharePoint columns to blueprint section fields.
FilterOptional CAML or OData filter to limit rows returned.
Refresh modeOn demand or scheduled.

Field mapping​

After connecting, map the source data columns to blueprint section fields:

  1. In the connection settings, click Field mapping.
  2. For each blueprint field in the section, select the matching source column.
  3. Set the Data type if the auto-detected type is incorrect.
  4. Click Preview data to see sample rows from the source.
  5. Save the mapping.

Refresh schedule​

Data connections can refresh automatically:

  • On edition open \u2014 refreshes when a contributor opens the edition for data entry.
  • Scheduled \u2014 refreshes at a configured interval (hourly, daily, on demand).
  • On output generation \u2014 refreshes just before the report output is generated.

Configure the refresh schedule in Manage connections → Refresh settings.

Security considerations​

  • Use service accounts (not personal accounts) for SQL Server and SharePoint connections to avoid connection failures when the configuring user leaves the project.
  • Store connection credentials in the Kazinex secure credential store \u2014 do not embed credentials in query strings.
  • Apply the principle of least privilege: the connecting account should only have SELECT access to the tables or views needed.
  • Review active connections quarterly and remove any that are no longer used.