BC Observatoryunofficial, made by waldo
tableAdministration & Setupofficial - Microsoftderived - from the source, no model text

Table 9171 "Profile Import"

Base Application · System.Environment.Configuration

Open in Claude9171.mdSource on GitHub

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-30unchanged

Neighbourhood 1 connected objects and pages

Page 9199 "Profile Import Wizard" (pages and codeunits on it)Profile Import Wizard

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.

Base Application · System.Environment.Configuration · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
DataClassification CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 App ID Guid — DataClassification SystemMetadata
2 Profile ID Code[30] Specifies an ID that is used to identify the profile (role). There can be more than one profile with the same ID if they come from different extensions. via Page 9199 “Profile Import Wizard”
3 Exists Boolean — DataClassification SystemMetadata
4 Selected Boolean Specifies that the profile from the package will be imported. via Page 9199 “Profile Import Wizard” DataClassification SystemMetadata

Keys

  • PK: App ID, Profile ID (clustered)

Triggers

OnInsert

Pages and codeunits on this table

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: "table", object_name: "Profile Import"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources