Before connecting a farm to Datamars Livestock, it's worth understanding what information is shared, who can manage the connection, and what happens if you remove it.
What data is shared?
Weight session information is imported from Datamars Livestock into Trev. For each session, Trev brings across:
The date the session took place
The session name
The number of animals weighed
The average liveweight
The lightest and heaviest liveweight
Each animal's weight, along with its electronic tag (EID) and visual tag (VID) numbers
The connection is one-way only. Information recorded in Trev is never sent back to Datamars Livestock.
Who can create and manage the connection?
To connect a farm, you must:
Have Full Access or Authorised access to the farm in Trev.
Have a Trev Pro subscription for that farm.
Important to note: Only the person who created a connection can change or remove it. Other users with Full Access, Authorised or Editor access can view the connection, but they won't be able to edit or delete it.
If the person who created the connection is no longer involved with the farm, get in touch with our team and we'll help you regain access.
Once weight events have been imported into Trev, this restriction no longer applies. Anyone with permission to edit weight events can assign a mob, add notes and complete their normal weekly reporting.
How your data is shared
Your data is transmitted securely from Datamars Livestock to Trev.
Trev checks for new weight sessions several times a day, so a session recorded in the morning will usually appear in Trev by the afternoon. If you need it sooner, you can trigger a manual sync at any time.
Imported sessions appear in the Weights module of the relevant weekly report as either Draft or Confirmed events, depending on how you've configured the connection.
Removing a connection
Important to note: Deleting a connection also removes every weight event that was imported through it. This action can't be undone.
If you simply want to stop importing new sessions, set an end date on the connection's synchronisation range instead. This stops future imports while leaving all existing weight events in Trev.
Need a hand? If something doesn't look right or you have questions about your connection, get in touch with us using the chat bubble in the bottom left corner of Trev. We'll be happy to help.