enumIntegration & APIsofficial - Microsoftderived - from the source, no model textobsolete - pending
Enum 6185 "EDoc Vendor Matching Scope"
EDocument · Microsoft.eServices.EDocument.Processing.Import
Across versionsobsolete pending since 27.0
- BC23-28not present
- BC29-30present
EDocument · Microsoft.eServices.EDocument.Processing.Import · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
| Extensible | false |
| ObsoleteState | Pending |
| ObsoleteTag | 27.0 |
| ObsoleteReason | Replaced with experiment-based matching. |
Values
| Ordinal | Name | Caption | Notes |
|---|---|---|---|
| 0 | Same Vendor | Same vendor | |
| 2 | Any Vendor | Any vendor |
Deprecations
- object: Pending 27.0 (#if not CLEANSCHEMA30), “Replaced with experiment-based matching.”
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "enum", object_name: "EDoc Vendor Matching Scope"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.