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

Codeunit 9453 "File Scenario Impl."

System Application · System.ExternalFileStorage

Across versions

  1. BC23-25not present
  2. BC26added
  3. BC27unchanged
  4. BC281 procedures added
  5. BC29-30unchanged

Neighbourhood 5 connected objects and pages

Codeunit 9452 "File Scenario" (calls, 7 links)File ScenarioCodeunit 9450 "File Account" (calls, 4 links)File AccountCodeunit 9451 "File Account Impl." (calls, 3 links)File Account Impl.Page 9452 "File Scenario Setup" (calls)File Scenario SetupPage 9454 "File Scenarios for Account" (calls)File Scenarios for Account

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

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

Properties

Property Value
Access Internal
Permissions tabledata “File Scenario” = rimd

Procedures

  • GetFileAccount(Scenario: Enum "File Scenario"; var TempFileAccount: Record "File Account" temporary): Boolean
  • GetSpecificFileAccount(Scenario: Enum "File Scenario"; var TempFileAccount: Record "File Account" temporary): Boolean + BC28
  • SetFileAccount(Scenario: Enum "File Scenario"; TempFileAccount: Record "File Account" temporary)
  • UnassignScenario(Scenario: Enum "File Scenario")
  • GetScenariosByFileAccount(var TempFileAccountScenario: Record "File Account Scenario" temporary): Get a list of entries, representing a tree structure with file accounts and the scenarios, assigned to each account.
  • AddScenarios(TempFileAccountScenario: Record "File Account Scenario" temporary): Boolean
  • GetAvailableScenariosForAccount(TempFileAccountScenario: Record "File Account Scenario" temporary; var TempFileAccountScenarios: Record "File Account Scenario" temporary)
  • ChangeAccount(var TempFileAccountScenario: Record "File Account Scenario" temporary): Boolean
  • DeleteScenario(var TempFileAccountScenario: Record "File Account Scenario" temporary): Boolean

Plus 3 local procedures.

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Called by

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

Evidence 1 sources