A company uses Dynamics 365 Finance. The company deploys a custom table named LoyaltyCustomerTable. The table has a 1:1 relationship with a table named CustTable. Both tables contain a unique field…

Question

Options

• ACreate a foreign key relation on LoyaltyCustomerTable with Related Table set to CustTable and
• BCreate foreign key relation on CustTable with Related Table set to LoyaltyCustomerTable and
• CCreate an index on CustTable for AccountNum.
• DCreate a foreign key relation on LoyaltyCustomerTable with Related Table set to CustTable and

• A
  46% (11)
• B
  8% (2)
• C
  17% (4)
• D
  29% (7)

Explanation

Create foreign key relation between the tables. Create the relation on LoyaltyCustomerTable as it needs the index. Include RecID in the index (not AccountIdx). Note: RecId stands for Record Identifier. It is often called RowId (row identifier). It is a unique and incremental value stored with each and every row of the table. Table index properties The following table describes the properties that are available for indexes on tables. * AllowDuplicates If you set this property to Yes, the index can be non-unique. If you don't create at least one unique index, a unique index is created by combining the first index and the RecId. * CreateRecIdIndex Specify whether an index on the Record ID field is created. https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-ref/application-explorer-

No community discussion yet for this question.