Overview
References are the ID mappings that link records between your two connected platforms. When Junipeer syncs a record — such as an order from your e-commerce platform to your ERP — it creates a reference that connects the source ID to the corresponding target ID. This is how Junipeer knows which records are already synced and avoids creating duplicates.
You can find the References page in the left sidebar of any integration.
Reference list
Like the Entities page, references are organized by data type using tabs at the top:
Articles — product/article ID mappings
Customers — customer ID mappings
Orders — order/invoice ID mappings
Stock — stock record mappings
Each reference shows the source platform ID and the target platform ID side by side.
Managing references
Viewing references
Browse or search references to understand how records are linked between platforms. This is useful for:
Verifying that a specific order was correctly mapped to the right invoice
Debugging sync issues where records appear duplicated or mislinked
Answering questions like "What is the ERP invoice number for e-commerce order #1234?"
Adding a reference
You can manually add a reference to link two existing records. This is useful when:
Records were created manually in both platforms before the integration was set up
A reference was accidentally deleted and you need to re-establish the link
Editing a reference
If a reference points to the wrong record, you can edit it to correct the mapping.
Deleting a reference
You can delete individual references. Important: deleting a reference does not delete the records in either platform — it only removes the link between them. This means:
The record still exists in both platforms
Junipeer no longer knows they are related
If the source record is synced again, Junipeer will create a new record in the target platform instead of updating the existing one
This can be useful when you want to re-create a record from scratch, but be cautious — it can lead to duplicates if not managed carefully.
Delete all references
There is also an option to delete all references for a given entity type. Use this with extreme caution. Deleting all references means that the next sync will treat every record as new, potentially creating duplicate records in the target platform.
This option is sometimes used during initial setup when testing with sample data, or when migrating to a completely fresh configuration.
When to use References vs. Entities
Both pages show synced data, but they serve different purposes:
| | References | Entities | |---|---|---| | Shows | ID mappings between platforms | Full record details and sync history | | Use for | Looking up which records are linked | Debugging sync errors, inspecting data | | Can modify | Yes (add, edit, delete mappings) | Limited (retry sync) |
Tips
If records are being duplicated in the target platform, check References to see if the mapping was lost or never created.
Before deleting references, consider whether you actually need to re-sync the data, or if editing the reference would be a safer option.
References are created automatically during normal syncing — you typically only need to manage them manually when troubleshooting.
For historical data that was created before the integration, you may need to manually add references or use the Time History page to backfill.