eForms Mobile Replicate – Exposing Tables from your Database as Data Sources

eForms Mobile Replicate – Exposing Tables from your Database as Data Sources

Using Platform Replicate for Real-Time Data Source

This article is an extract from the Replicate Installation Guide (PDF). For full context and comprehensive references, please consult the complete manual.

If you have local data that needs to be continuously available to your mobile apps, Platform Replicate is the most efficient method. By using this feature, the app requests rows directly from your local SyncData database via the Replicate API, eliminating the need to store that data on our cloud platform.


Terminology Reference: Replicate vs. Platform

TermComponentDefinition & RolePhysical Location
eForms Mobile ReplicateThe SoftwareThe standalone Windows/IIS web application that performs the actual data synchronization.On-Premise (Customer or Vendor Server)
Platform ReplicateThe LinkThe specific “Hook” setting inside a Data Source that tells the Platform where to pull data from.Cloud (eForms Mobile Portal)
SyncData DatabaseThe StorageThe local SQL Server database where eForms Mobile Replicate writes incoming form data.Local SQL Server

How it Works

Replicate exposes a REST API endpoint at:

https://{Your-Domain-or-IP}/api/v2/datasources

When the app requests data, the Replicate application performs a GET function that maps your platform Data Source to a matching table name in your SQL database.


Setup Instructions

Database Preparation

  • Create your desired data tables within the SyncData database.
  • Naming Convention: The SQL table name must exactly match the External ID assigned to the Data Source in the platform.
  • Column Order: Ensure the columns in your platform Data Source follow the exact same order as the columns in your SQL table.

Platform Configuration

  1. Log in to the Platform and navigate to Data Hub > Data Sources.
  2. Select your target Data Source and click Settings.
  3. Verify the External ID field matches your SQL table name.
  4. Hover over Add Connector and select Platform Replicate.
  5. Enter your eForms Mobile Replicate installation’s target URL (e.g., https://sync.yourdomain.com/api/v2/datasources) and click Save.

Global Configuration

If you are managing multiple Data Sources, avoid entering the URL manually every time:

  1. Go to Organization Setup > Integrations > Global Service Endpoints.
  2. Set the Data Source Replicate to your Replicate API endpoint.
  3. In your individual Data Source connectors, simply select the “Use Global Replicate URL” checkbox.

Implementation Checklist

  • Does the External ID match the SQL Table Name?
  • Does the Column Order in the platform match the SQL Table Schema?
  • Is your Replicate server accessible via HTTPS?

Troubleshooting Platform Replicate Connections

When Platform Replicate isn’t pulling data, it’s usually a mismatch between the IIS server’s security and the platform’s request. Here is a troubleshooting table with common codes and resolutions:

Error CodePotential CauseRecommended Fix
404 Not FoundNaming Mismatch: The platform cannot find a table matching the External ID.Ensure the External ID in the Platform exactly matches the SQL Table Name in the SyncData database.
401 UnauthorizedSecurity Layer: Your Replicate IIS site is blocking the request.Verify that Anonymous Authentication (or your specific API key) is correctly configured in IIS for the /api/v2/ path.
403 ForbiddenIP Restriction: Your server is blocking the Platform’s IP addresses.Whitelist our Platform’s outbound IP addresses in your corporate firewall or Windows Firewall.
500 Internal ErrorSQL Permissions: Replicate cannot read the table.Ensure the database user assigned to Replicate has db_datareader permissions on the SyncData database.
Timeout / Connection RefusedNetwork Path: The URL is not accessible from the public internet.Verify your Sync.SelfUrl is reachable. Try browsing to the URL from an external network (like a mobile hotspot) to test.
Data MismatchSchema Change: Column count or order does not match.Ensure the number of columns in your Platform Data Source matches the SQL Table. Columns are mapped by index (order), not name.

How to Test Your Endpoint

Before configuring the Platform, you can test if your Replicate API is “alive” by navigating to your data source URL in a browser:

https://{Your-Domain-or-IP}/api/v2/datasources

What to look for: You should receive a JSON response or a prompt for credentials. If the page fails to load entirely, the issue is likely with your IIS Binding or Firewall, rather than the Replicate software itself.

    • Related Articles

    • eForms Mobile Replicate – Push Form Entry Data to your Database

      How Data is Structured in eForms Mobile Replicate When a form is submitted, eForms Mobile Replicate automatically creates a table in your local SyncData database. Table Name: Derived from the Form Screen’s External ID. Columns: Derived from the Data ...
    • eForms Mobile Replicate – FAQs

      General & Branding What database types does Replicate support? Replicate currently supports Microsoft SQL Server. We are actively working to expand compatibility with other database engines in future updates. Can I white-label Replicate with my own ...
    • eForms Mobile Replicate – User-Level Data Filtering

      By default, eForms Mobile Replicate sends every row in a table to every user. To ensure users only see the data relevant to them, you can implement User-Level Filtering. This article is an extract from the Replicate Installation Guide (PDF). For full ...
    • eForms Mobile Replicate – Seamless Data Synchronization

      While our platform offers “baked-in” cloud connectors and a robust Integration API, we recognize that many organizations have a foundational requirement: accessing data within their own local SQL environment. Replicate is a standalone web application ...
    • eForms Mobile Replicate – Optimizing Large Datasets with Incremental Updates

      By default, the mobile app downloads all Data Source rows during every sync. For large datasets, this can cause slow performance and high data usage. To solve this, you can enable Incremental Updates. This tells the app to only download rows that ...