📘 Screen: Sector
The sector groups the farm's areas together — "Boa Vista", "Nascente", "São João", "Entre Rios". In practice, sectors are created by the Field record: when someone types a new sector in the field's Sector field, it starts to exist and shows up in this list on its own.
That is why this is an auxiliary screen, not the starting point. You come here for two reasons: to say which group each sector belongs to, and to enter the Reference/Integration ID when the farm exchanges data with an external system. Day to day, the New button is almost never used.
📍 Location in the system
Menu: Basic > Sector
🧩 Main function
Complete the information on sectors that were already created from the field records — the group and the integration code —, and let you deactivate a sector that is no longer in use.
🌱 Where sectors come from
From the field. In the Field record, the Sector field accepts a new value typed on the spot, and that is how the farm builds up its internal division: each field gets the name of the unit it belongs to. The list shown there combines the sectors already used in fields with the ones that exist in this record, so both sides always see the same set.
The practical consequence is that if a sector is spelled two ways in the fields ("Boa Vista" and "BOA VISTA"), it becomes two sectors. Standardizing the spelling in the field is what prevents a duplicated list here.
📝 Main fields
| Field | Description |
|---|---|
| Code | Short identifier for the sector. It is usually left blank, since the sector comes from the field. |
| Name/Description | Required. The name of the unit, exactly as it is spelled in the fields: "Boa Vista", "Nascente", "Primavera". |
| Group | This is the main reason to open this screen. A level above the sector, to bring several units together in a single view — for example, the sectors Boa Vista, Nascente and São João all in the group "Lucas", and Campinas and Jandaira in "Tapurah". |
| Reference ID | The other reason. The sector's code in the external system, when there is an integration. It becomes required when the company is set up to require an integration ID — in that case the system refuses to save without it. |
| Zoom | Map zoom level for that sector. On most farms it stays at zero; it is only filled in when a specific map dashboard needs it. |
| Latitude / Longitude | Reference point for the sector, in the same situation as Zoom: they are usually left at 0.0. |
| Active | Uncheck it to remove the sector from the lists without deleting the entries that already used it. |
The list shows Code, Description, Group, Zoom, Latitude, Longitude, Active and Reference/Integration ID, with search on each column.
🧾 Where the sector shows up
Besides the crop sector filters — which read the sector saved on the field —, the sectors in this record feed the Sector field in the header of Inventory Movement (Inbound & Outbound). That field only appears on the screen when at least one sector is registered.
- Several sectors can be read together through the group, instead of one by one
- The integration recognizes each unit by the external system's code
- A sector that is no longer used is deactivated without erasing history
❓ Frequently asked questions
Do I need to register sectors before registering fields?
No. It is the other way around: type the sector directly in the Sector field of the Field record and it starts to exist on its own. This screen is for completing what the field does not ask for — the group and the integration code.
What is the Group field for?
To bring several sectors together in a layer above, usually by region, municipality or manager. That way "Boa Vista", "Nascente" and "São João" can be added up as a single block, while still existing separately.
The same sector shows up twice in the list. How do I fix it?
This happens when the name was spelled differently in the fields — "Boa Vista" and "BOA VISTA" become two sectors. Standardize the spelling in the Sector field of the fields involved and then deactivate the leftover record.
Is the Reference ID field required?
Only when the company is set up to require an integration ID. In that case the system refuses to save the sector without that code, because that is how the external system recognizes the area. In other companies the field can stay empty.
What is the difference between a branch and a sector?
The branch is the unit with its own CNPJ (Brazilian company tax ID) — it is the one that issues invoices and closes inventory. The sector is an internal division of that branch, to separate production units that share the same CNPJ. If the areas have different CNPJs, they are branches; if they share the same one, they are sectors.