Table 91 - Events
- This article introduces the event integration layout fields. To better understand the concept behind events, see our article on Event Concept.
- The integration of this table varies according to the type of event that is taking place.
- Example:
- “The seller wants to create a Visit without Sale event.”
- Example:
- In this case, the event must be sent together with:
| Order | Field Description | Format and Size | Required | Version | Note |
| 1 | Table Identifier (IDENTIFICADOR) | FIXO=91 (2) | Yes | 2.33 | |
| 2 | Unique Event Identifier of Demander (idEvento) | Integer (10) | No | 2.33 | |
| 3 | Unique Customer Identifier in Demander (uniqueIdCliente) | Text (50) | No | 2.33 | |
| 4 | Customer code (codCliente) | Integer | Yes | 2.33 | |
| 5 | Unique Order Identifier in Demander (uniqueIdPedido) | Text (50) | Yes | 2.33 | |
| 6 | Event number (numEvento) | Integer (10) | Yes | 2.33 | Events registered by the seller assume the number “0”, this value is only updated after being returned by the ERP. |
| 7 | Event type code (codTipoEvento) | Text (20) | Yes | 2.33 | |
| 8 | Date and time of record creation (dataInclusao) | DateTime | No | 2.33 | |
| 9 | Scheduling date and time (dataAgendamento) | DateTime | Yes | 2.33 | |
| 10 | Date and time of the event (dataRealizacao) | DateTime | No | 2.33 | |
| 11 | Contact (contact) | Text | No | 2.33 | |
| 12 | Description (description) | Text | No | 2.33 | |
| 13 | Conclusion (conclusion) | Text | No | 2.33 | |
| 14 | Marking event closed (closed) | Integer (1) | No | 2.33 | 1 = Closed or 0 = Not Closed |
| 15 | Seller (codVendedor) | Integer (10) | Yes | 2.33 | |
| 16 | Event Control Identifier (uniqueId) | Text (50) | Yes | 2.36.3 | |
| 17 | Event Status Code (codStatusEvento) | Text (50) | Yes | 3.21 | Allowed options: A → Open G → Waiting for position (or in progress) R → Done (or completed) C → Canceled |
| 18 | Latitude (latitude) | Text (50) | No | 3.22 | |
| 19 | Longitude (longitude) | Text (50) | No | 3.22 | |
| 20 | codVendedorContato | Integer (10) | No | 4.12 | Code of the seller who will be responsible for attending the event |
Registration Example:
91|4||1|V117188-15289848735041|1|1|2018-06-20|2018-06-20|2018-06-30|André||1|0|1|123123123|A||