# C1.Win.C1DynamicHelp.TopicMap.Conflicts

## Content

<div class="doc-site-dotnet-api-container">



<h1 id="C1_Win_C1DynamicHelp_TopicMap_Conflicts_" data-uid="C1.Win.C1DynamicHelp.TopicMap.Conflicts*">Conflicts Property
</h1>
<div class="markdown level0 summary"></div>
<div class="markdown level0 conceptual"></div>



<a id="C1_Win_C1DynamicHelp_TopicMap_Conflicts_" data-uid="C1.Win.C1DynamicHelp.TopicMap.Conflicts*"></a>
<h4 id="C1_Win_C1DynamicHelp_TopicMap_Conflicts" data-uid="C1.Win.C1DynamicHelp.TopicMap.Conflicts">Conflicts</h4>
<div class="markdown level1 summary"><p>Gets an array of conflicting map items.</p>
</div>
<div class="markdown level1 conceptual"></div>
<h5 class="declaration">Declaration</h5>
<div class="codewrapper">
  <pre><code class="lang-csharp hljs">public Conflict[] Conflicts { get; }</code></pre>
</div>
<div class="codewrapper">
  <pre><code class="lang-vbnet hljs">Public ReadOnly Property Conflicts As Conflict()</code></pre>
</div>
<h5 id="C1_Win_C1DynamicHelp_TopicMap_Conflicts_remarks">Remarks</h5>
<div class="markdown level1 remarks"><p>A conflict exists between two map items, one static and the other dynamic,
when they refer to the same UI element. In such a case, the precedence is with the dynamic 
map item, no error is generated, the static map item is silently ignored.</p>
<p>Usually, there is no need to worry about these conflicts (mostly because static and dynamic
mappings are rarely mixed, usually either only static or only dynamic mappings are used),
but in case the programmer wants to know which items are in conflict with each 
other, that can be done using this property.</p>
</div>
</div>
