codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 9459 "Default File Scenario Impl."

System Application · System.ExternalFileStorage

Across versions

  1. BC23-27not present
  2. BC28added
  3. BC29-30unchanged

System Application · System.ExternalFileStorage · BC28-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal

Procedures

  • BeforeAddOrModifyFileScenarioCheck(Scenario: Enum "File Scenario"; Connector: Enum System.ExternalFileStorage."Ext. File Storage Connector"): Boolean: Called before adding or modifying a file scenario.
  • GetAdditionalScenarioSetup(Scenario: Enum "File Scenario"; Connector: Enum System.ExternalFileStorage."Ext. File Storage Connector"): Boolean: Called to get additional setup for a file scenario.
  • BeforeDeleteFileScenarioCheck(Scenario: Enum "File Scenario"; Connector: Enum System.ExternalFileStorage."Ext. File Storage Connector"): Boolean: Called before deleting a file scenario.
  • BeforeReassignFileScenarioCheck(CurrentScenario: Enum "File Scenario"): Boolean: Called before reassigning a file scenario from one to another.

Implements

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "Default File Scenario Impl."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources