Table 205 "Resource Unit of Measure"

Base Application · Microsoft.Projects.Resources.Resource · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Resource Unit of Measure
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	Resource No. Δ BC28	Code[20]	Specifies the number of the resource.	TableRelation Table 156 “Resource”; NotBlank
2	Code Δ BC28	Code[10]	Specifies one of the unit of measure codes that has been set up in the Unit of Measure table.	TableRelation Table 204 “Unit of Measure” (Unit of Measure); NotBlank
3	Qty. per Unit of Measure Δ BC28	Decimal	Specifies the number of units of the code. If, for example, the base unit of measure is hour, and the code is day, enter 8 in this field.
4	Related to Base Unit of Meas. Δ BC28	Boolean	Specifies that the unit of measure can be calculated into the base unit of measure. For example, 2 days equals 16 hours.
721	Coupled to Dataverse Δ BC28	Boolean	Specifies that the resource unit of measure is coupled to a unit of measure in Dynamics 365 Sales.	FlowField: exist(“CRM Integration Record” where(“Integration ID” = field(SystemId), “Table ID” = const(Database::“Resource Unit of Measure”)))

Keys

Key1: Resource No., Code (clustered)

Trigger event subscribers

OnBeforeModifyEvent: Codeunit 5402 “Unit of Measure Management” ClearResourceUnitOfMeasureRec

Procedures

3 local procedures, no public ones.

Triggers

OnDelete, OnRename

Relations

lookup page Page 210 “Resource Units of Measure”
Resource No.: TableRelation Table 156 “Resource”
Code: TableRelation Table 204 “Unit of Measure”
Coupled to Dataverse: CalcFormula Table 5331 “CRM Integration Record”

Referenced by

21 fields in 20 objects relate to this table (TableRelation or CalcFormula).

Table 5870 “BOM Buffer”: BOM Unit of Measure Code, Unit of Measure Code
Table 1003 “Job Planning Line”: Unit of Measure Code
Table 169 “Job Ledger Entry”: Unit of Measure Code
Table 171 “Standard Sales Line”: Unit of Measure Code
Table 174 “Standard Purchase Line”: Unit of Measure Code
Table 207 “Res. Journal Line”: Unit of Measure Code
Table 210 “Job Journal Line”: Unit of Measure Code
Table 37 “Sales Line”: Unit of Measure Code
Table 39 “Purchase Line”: Unit of Measure Code
Table 5137 “Job Planning Line Archive”: Unit of Measure Code
Table 5476 “Sales Invoice Line Aggregate”: Unit of Measure Code
Table 5902 “Service Line”: Unit of Measure Code
Table 5997 “Standard Service Line”: Unit of Measure Code
Table 6012 “Service Line Archive”: Unit of Measure Code
Table 7001 “Price List Line”: Unit of Measure Code Lookup
Table 7022 “Price Worksheet Line”: Unit of Measure Code Lookup
Table 83 “Item Journal Line”: Cap. Unit of Measure Code
Table 90 “BOM Component”: Unit of Measure Code
Table 901 “Assembly Line”: Unit of Measure Code
Table 911 “Posted Assembly Line”: Unit of Measure Code

Pages and codeunits on this table

Page 210 “Resource Units of Measure” (source 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: "Resource Unit of Measure"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.