pageProjectsofficial - Microsoftderived - from the source, no model text

Page 5403 "Resource Unit Group List"

Base Application · Microsoft.Projects.Resources.Resource

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Table 5400 "Unit Group" (relates to)Unit GroupCodeunit 5330 "CRM Integration Management" (calls, 2 links)CRM Integration ManagementCodeunit 5331 "CRM Coupling Management" (calls)CRM Coupling Management

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 · Microsoft.Projects.Resources.Resource · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Resource Unit Group List
SourceTable Unit Group
PageType List
UsageCategory Lists
ApplicationArea All

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
GroupName Code CodeLbl Specifies the code of the record.
Resource No. Source No. Specifies the resource number that associated with the record.
Resource Name SourceNameLbl Specifies the resource name that associated with the record.
Coupled to Dataverse Coupled to Dataverse Specifies that the resource unit group is coupled to a unit group in Dynamics 365 Sales.

Actions

Group Action ToolTip Runs
Dynamics 365 Sales Unit Group Open the coupled Dynamics 365 Sales unit group.
Synchronize Send updated data to Dynamics 365 Sales.
Coupling Set Up Coupling Create or modify the coupling to a Dynamics 365 Sales unit group.
Delete Coupling Delete the coupling to a Dynamics 365 Sales unit group.
Dynamics 365 Sales Synchronization Log View integration synchronization jobs for the unit group table.

Triggers

OnAfterGetRecord, OnAfterGetCurrRecord, OnOpenPage

Relations

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.

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: "page", object_name: "Resource Unit Group List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources