codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 437 "IC Navigation"

Base Application · Microsoft.Intercompany

Across versions

  1. BC23-25present
  2. BC262 procedures added, 1 procedures removed
  3. BC27-30unchanged

Base Application · Microsoft.Intercompany · BC23-30 · source at ea08af5e · facts from BC29

Events published

  • OnNavigateToPurchaseDocumentOnDocumentTypeCaseElse(DocumentNo: Code[20]; ICDirectionType: Enum "IC Direction Type"; ICPartnerCode: Code[20]; DocumentType: Enum "IC Transaction Document Type"; var OpenDoc: Boolean) (integration): Integration event raised when navigating to purchase documents for custom document types. Enables custom navigation logic for extended IC transaction document types.
  • OnNavigateToSalesDocumentOnAfterCheckDocumentType(DocumentNo: Code[20]; ICDirectionType: Enum "IC Direction Type"; ICPartnerCode: Code[20]; ICTransactionDocumentType: Enum "IC Transaction Document Type"; var ShouldNavigateToDoc: Boolean) (integration): Integration event raised when navigating to sales documents after document type validation. Enables custom navigation logic for extended IC transaction document types.

Procedures

  • NavigateToDocument(HandledICInboxTrans: Record "Handled IC Inbox Trans.") + BC26 − BC26: Navigates to the related document from a handled IC inbox transaction. Opens the corresponding sales or purchase document based on transaction details.
  • NavigateToDocument(ICOutboxTransaction: Record "IC Outbox Transaction") + BC26 − BC26: Navigates to the related document from an IC outbox transaction. Opens the corresponding sales or purchase document that was sent to partner.
  • NavigateToDocument(HandledICOutboxTrans: Record "Handled IC Outbox Trans.") + BC26 − BC26: Navigates to the related document from a handled IC outbox transaction. Opens the corresponding sales or purchase document that was previously sent.

Plus 11 local procedures.

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: "IC Navigation"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources