📘 Screen: Integration problems

When the farm exchanges data with an external system (machine telemetry, the manufacturer's platform, an ERP), not everything gets in. An operation arrives from equipment that is not registered, or from a field whose name upCampo does not recognize. Instead of disappearing, these records stop here, with a description of what blocked them.

It is a read-only screen: it shows what got stuck and helps you find out why. The fix is made in the records, or in Mapping - Integration, when the problem is just a different name.

📍 Location in the system

Menu: File > Integration problems

🧩 Main function

List the records the integration could not import and show, for each one, whether the equipment and the field that came from outside exist in upCampo's records.

📋 The list

Shows Sorting, Date, Description (the reason for the problem), Type, Equipment, Variety/Cultivar, Field, Field ID and JD ID, with search on each column. The Reload button refreshes the list.

🔍 Diagnosing the record

When you select a row, the form shows the data as it came from the external system (date, description, equipment, variety, field, the identifiers and the raw content received) and, below a divider line, two check fields:

• Equipment - upCampo: the system looks up the matching fleet by chassis number. If it finds it, it shows "Equipment found!" right below the field; if not, "Equipment not found!"
• Field - upCampo: the same check for the field

That pair of messages shows the way: "not found" means the record is missing in upCampo, or it exists under another name, and in that case the mapping solves it.

The screen changes nothing: there is no save or delete, only Cancel to go back to the list. After fixing the record, the integration itself reprocesses the item.

❓ Frequently asked questions