To establish a primary key, you must first create a physical index structure within the table designer. After creating the index, you associate the specific field (FMAssetId) with it. Because a primary key requires uniqueness, the Allow Duplicates property must be explicitly set to No. Finally, once the unique index is defined, you go to the table's top-level properties to assign that index as the Primary Index. This metadata configuration ensures data integrity and allows the kernel to identify the unique record identifier for the table.

Microsoft Learn (Official Documentation): Table Index Properties, Section: "AllowDuplicates". Specifies that for unique indexes (required for primary keys), this property must be set to No.

Microsoft Learn (Official Documentation): Tables in Development, Section: "Table Properties". Identifies the PrimaryIndex property as the mechanism to define the unique index used for the table's primary key.

Microsoft Dynamics 365 Finance and Operations Developer Guide: How to: Create an Index. Outlines the workflow of creating the index node, adding fields via drag-and-drop, and setting uniqueness before assignment to table properties.

Dynamics 365 Standard Design Patterns: Primary Key and Natural Key design. Confirms that PrimaryIndex is the metadata property used to enforce the primary key constraint in the underlying SQL database via the AOT.