共用方式為


<ReferencingAttributeRequiredRule> (RibbonDiffXml)

適用於: CRM 2016 on-prem, CRM Online

規則,偵測是否需要實體的參照屬性。

語法

<ReferencingAttributeRequiredRule 
 Default=["0" | "1" | "true" | "false"]
 InvertResult=["0" | "1" | "true" | "false"]
 />

屬性和元素

The following describes the attributes, child elements, and parent elements.

屬性

Attribute Description Type Usage

Default

設定當無法判斷實際值時,規則的預設傳回值。

Boolean

Optional

InvertResult

變換規則傳回值的正負號。

Boolean

Optional

子元素

此元素沒有子元素。

上層元素

Element Description

<DisplayRule> (RibbonDiffXml)

指定用於顯示功能區元素或命令定義中 DisplayRule 參照的規則定義。

<Or> (RibbonDiffXml)

指定一組必須同時評估的規則。

備註

This is a very specific rule for a very specific case. Use this rule when there is a relationship bound subgrid or an associated grid on the page. This rule will test whether the referencing attribute used in the relationship is required. This rule is used to hide the Add Existing <record type> button when it isn’t appropriate to display it.

In an entity relationship the lookup field in the related record (the referencing attribute) may be required or not. For example, the Regarding field of an activity is not required yet the Potential Customer field of an opportunity is required. The Add Existing Activity button will set the Regarding field value to the current record context and it can only work if the Regarding field doesn’t already have a value. All Opportunity records have a value in their Potential Customer field, so it never makes sense to display an Add Existing Opportunity button. This rule detects that the referencing attribute is required and therefore returns true.

元素資訊

XPath

//RibbonDiffXml/RuleDefinitions/DisplayRules/DisplayRule/ReferencingAttributeRequiredRule
|
//RibbonDiffXml/RuleDefinitions/DisplayRules/DisplayRule/OrRule/Or/ReferencingAttributeRequiredRule

Schema Name

ReferencingAttributeRequiredRuleType

Validation File

RibbonTypes.xsd

Can be Empty

Yes

請參閱

其他資源

Ribbon XML reference
自訂命令和功能區

Microsoft Dynamics CRM 2016 and Microsoft Dynamics CRM Online
Send comments about this topic to Microsoft.
© 2015 Microsoft. All rights reserved.