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 Names of your form fields.
Automatic Metadata Mapping
In addition to your custom form fields, every table includes the following system metadata columns:
| Column Name | Description |
| Id | Unique identifier for the form entry. |
| ItemNo | Row index (increments for each row in a Repeated Group). |
| FormVersion | The specific version of the form used for submission. |
| Latitude / Longitude | GPS coordinates captured at the time of saving. |
| StartTime | Local timestamp when the user started the entry. |
| ReceivedTime | UTC timestamp when the entry hit the Cloud Platform. |
| CompleteTime | Timestamp when the entry was fully synced to your local server. |
| UserFirstName/LastName | The name of the mobile user who submitted the data. |
Media Files: If Sync.Download.Media is set to true in your web.config, Replicate will automatically download all images, signatures, and files to your designated MediaFiles folder.
Configuring the Form Entry Push
To move data from the cloud to your local SQL Server, you must configure a REST Connector within the Platform Replicate dashboard.
Setup Steps
- Define the Table Name: * In the App Workshop, open your Form settings.
- Set a unique External ID. This must be the name you want for your SQL table.
- Add the Connector:
- Go to the Connectors page of your Form.
- Click Add Connector and select REST.
- Configure the Destination:
- Target URL: Enter your local Replicate endpoint:
https://{Your-Domain}/api/v1/formentries. - Format: Ensure the body is sent as JSON.
- Target URL: Enter your local Replicate endpoint:
- Save & Test:
- Submit a test entry from the mobile app.
- eForms Mobile Replicate will detect the incoming POST, create the table (if it doesn’t exist), and insert the row.
The “Handshake” Verification
Once the connector is saved in the Platform, and a test entry has been submitted in your mobile app.
On the form’s connector logs in Form Entries Feed, you should see:
| If you see… | It means… | Action |
| New Table in SQL | Success! | Platform Replicate successfully commanded eForms Mobile Replicate to build the schema. |
| Connector Error (Red) | Connection Blocked. | Check your local server’s firewall; it likely blocked the incoming request from the Platform. |
| No Table / No Error | Sync Delay. | Check the “Queue” status in eForms Mobile Replicate to see if the packet is waiting to be processed. |
Critical Requirements Checklist
- External ID: Is it unique and valid for a SQL table name (no spaces/special characters)?
- API Endpoint: Is your server’s
/api/v1/formentriespath accessible by the Platform? - Media Config: Is
Sync.Download.Mediaenabled if you need photos/signatures?