Table 6104 "Service Participant"
EDocument · Microsoft.eServices.EDocument.Service.Participant
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 4 connected objects and pages
EDocument · Microsoft.eServices.EDocument.Service.Participant · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Public |
| Extensible | true |
| DataClassification | SystemMetadata |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Service | Code[20] | Specifies the E-Document service for which the participant is associated. | TableRelation Table 6103 “E-Document Service” (E-Document Service) |
| 2 | Participant Type | Enum “E-Document Source Type” | Specifies the type of participant associated with the E-Document service. | enum Enum 6123 “E-Document Source Type” |
| 3 | Participant | Code[20] | Specifies the participant associated with the E-Document service. | TableRelation Table 18 “Customer”, Table 23 “Vendor” (if (“Participant Type” = const(Customer)) Customer else if (“Participant Type” = const(Vendor)) Vendor) |
| 4 | Participant Identifier | Text[200] | Specifies the identifier of the participant associated with the E-Document service. | DataClassification CustomerContent |
Keys
- PK: Service, Participant Type, Participant (clustered)
Relations
- Participant: TableRelation Table 18 “Customer” (conditional)
- Participant: TableRelation Table 23 “Vendor” (conditional)
- Service: TableRelation Table 6103 “E-Document Service”
Pages and codeunits on this table
- Page 6150 “Service Participants” (source table)
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "Service Participant"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.