The Sold event (ECEvent code 14) allows you to update an animal's record to show that is has been sold and no longer belongs to the dairy. See the topics below for help with this event:
- Define Details for this Event
- What Happens When I Process Changes for this Event?
- Need Help Adding Animals to this Event?
The details listed below are typical for a Sold event; however, be aware that the details you see in the mobile app may vary based on the DC305DairyComp305 - VAS Dairy Management Software command that created the event. If any fields other than the animal IDIdentifier are required to process an animal, they are marked with an * (asterisk) symbol in the app.
The ID of the animal that has been sold. This field is automatically populated with the animal ID when you add an animal to the list. You can tap its ID number to view its CowCard.
Because the app expects you to add animals that are eligible to sell, it will display a warning before allowing you to add an animal if its meat withdrawal date has not expired. The app will not restrict you from adding these animals; it simply warns you of their status so that you can determine whether to continue.
The technician who added the animal to this event. Tap this field to select from a list of available technicians.
The names and numbers in the TechnicianTech is short for Technician. list come from the Technician Table in DC305. This table is optional in DC305, so if you do not see any names here in the mobile app, you need to make sure that a DC305 admin has created this table so that it can synchronize to the Platform. Once it has been created, a code number and name can be assigned to each technician, and members with DC305 admin permissions can add and remove technician names as necessary. The mobile app requires an active data or WiFi connection to synchronize updates.
The disposal code defines the reason for selling the animal. Tap this field to choose from a list of options.
The options in the Disposal Codes list come from the CARCondition Affecting Record. CAR codes are used by DHIA to determine the status of a cow’s record. This includes reason for disposal as well as reasons for the record not to be used for sire proofs. The DairyComp CAR table includes the 9 standard DHIA codes and allows users to add 7 additional codes to the table. table in DC305. If you require changes in the Platform mobile app, you should request that a user with admin permissions enter the updates in DC305. Once the CAR table is updated on‑premise, the Platform will receive those updates during the next scheduled data synchronization. The mobile app requires an active data or WiFi connection to synchronize updates.
The Remark field allows you to type any notes that you would like to include about this animal when adding it to the event. The remark you enter here will be included as additional information in the animal's record.
Note that you will only see this option in the mobile event when REMRemark or comment is included as a condition in the DC305 command that the Platform uses to create the event.
When DairyComp 305 receives the updates, it records a Sold event for each completed animal and records the EDAYEvent day as the date the event was completed in the mobile app.
See Processing Your Changes for more information on how the mobile app, the Platform, and DairyComp 305 work together to process your changes.
See the following topics:
- Create a New Event or Edit an Existing One
- Save Time when Adding Animals in Bulk
- Details Required to Process Animals in an Event
- Remove an Animal from an Event
Last Built: May 20, 2020