codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 6199 "E-Doc. Import Error Context"

EDocument · Microsoft.eServices.EDocument.Processing.Import

Across versions

  1. BC23-28not present
  2. BC29-30present

EDocument · Microsoft.eServices.EDocument.Processing.Import · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal

Events published

  • OnValidateFieldWithContext(FieldCaption: Text) (integration): Sets the context to describe a field being validated during e-document import.
  • OnSetAdditionalFieldContext(FieldName: Text; FieldNo: Integer; Value: Text) (integration): Sets the context to describe an additional field being applied

Event subscriptions

  • ValidateFieldWithContextSubscriber subscribes to Codeunit “E-Doc. Import Error Context” OnValidateFieldWithContext
  • SetAdditionalFieldContext subscribes to Codeunit “E-Doc. Import Error Context” OnSetAdditionalFieldContext

Procedures

  • HasContext(): Boolean: Returns whether a context message is currently set.
  • WrapErrorMessage(OriginalError: Text): Text: Wraps the original error message with the current context, if one is set.
  • ClearAdditionalFieldContext(): Clears the additional field context

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: "codeunit", object_name: "E-Doc. Import Error Context"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources