<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: RAP validation message targeting a composition associ... in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/rap-validation-message-targeting-a-composition-association-does-not/qaa-p/14516088#M4950993</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.sap.com/t5/user/viewprofilepage/user-id/2351487"&gt;@kristof_desaegera89d83&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is a known limitation in Fiori Elements OData V4. Validation messages targeted at a collection-valued association (_PackItems) are not automatically propagated to the generated sap.ui.mdc.MultiValueField&lt;/P&gt;&lt;P&gt;try,&lt;/P&gt;&lt;P&gt;Report the validation against a specific child field (e.g., PackItems-PackType) instead of the association.&lt;BR /&gt;If the error is at least one entry required use a parent-level message (page/object level)&lt;BR /&gt;Automatic red highlighting of MultiValueField for association-targeted RAP messages is generally not supported in current SAPUI5/Fiori Elements versions&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Sravan&lt;/P&gt;</description>
    <pubDate>Wed, 04 Nov 2026 08:41:14 GMT</pubDate>
    <dc:creator>sravan_aleshwaram</dc:creator>
    <dc:date>2026-11-04T08:41:14Z</dc:date>
    <item>
      <title>RAP validation message targeting a composition association does not highlight MultiValueField</title>
      <link>https://community.sap.com/t5/technology-q-a/rap-validation-message-targeting-a-composition-association-does-not/qaq-p/14515813</link>
      <description>&lt;P&gt;&lt;SPAN&gt;We are using SAPUI5 1.120 with a Fiori Elements OData V4 application based on RAP but also tested below question with UI versions up to 1.151.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Our application contains a parent entity &lt;/SPAN&gt;&lt;CODE&gt;&lt;SPAN&gt;_Items&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt; with a composition association &lt;/SPAN&gt;&lt;CODE&gt;&lt;SPAN&gt;_PackItems&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt;. A &lt;/SPAN&gt;&lt;CODE&gt;&lt;SPAN&gt;@UI.lineItem&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt; annotation referencing &lt;/SPAN&gt;&lt;CODE&gt;&lt;SPAN&gt;_PackItems.PackType&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt; automatically generates a &lt;/SPAN&gt;&lt;CODE&gt;&lt;SPAN&gt;sap.ui.mdc.MultiValueField&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt; in the table.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We perform RAP validations and return messages targeting individual fields. All normal scalar properties are correctly highlighted in red by Fiori Elements.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;However, when validating that &lt;/SPAN&gt;&lt;CODE&gt;&lt;SPAN&gt;_PackItems&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt; must contain at least one entry, we return an error targeting the association:&lt;/SPAN&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;SPAN&gt;$Parameter/_it/_Items(...)/_PackItems&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;SPAN&gt;The generated &lt;/SPAN&gt;&lt;CODE&gt;&lt;SPAN&gt;MultiValueField&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt; is not highlighted in red.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;Questions:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Does Fiori Elements OData V4 support automatic value-state handling for validation messages targeting collection-valued associations?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Is there a specific RAP &lt;/SPAN&gt;&lt;CODE&gt;&lt;SPAN&gt;%element&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;CODE&gt;&lt;SPAN&gt;%path&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt;, or OData message target syntax required to associate the error with the generated &lt;/SPAN&gt;&lt;CODE&gt;&lt;SPAN&gt;MultiValueField&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt;?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Should the validation message be reported against the parent entity's association or against the child entity's &lt;/SPAN&gt;&lt;CODE&gt;&lt;SPAN&gt;PackType&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt; property?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;Is this a known limitation of &lt;/SPAN&gt;&lt;CODE&gt;&lt;SPAN&gt;sap.ui.mdc.MultiValueField&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt; in SAPUI5?&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;SPAN&gt;We would prefer to use standard RAP/Fiori Elements message handling rather than manually setting the generated control's &lt;/SPAN&gt;&lt;CODE&gt;&lt;SPAN&gt;valueState&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Nov 2026 17:56:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/rap-validation-message-targeting-a-composition-association-does-not/qaq-p/14515813</guid>
      <dc:creator>kristof_desaegera89d83</dc:creator>
      <dc:date>2026-11-03T17:56:51Z</dc:date>
    </item>
    <item>
      <title>Re: RAP validation message targeting a composition associ...</title>
      <link>https://community.sap.com/t5/technology-q-a/rap-validation-message-targeting-a-composition-association-does-not/qaa-p/14516088#M4950993</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.sap.com/t5/user/viewprofilepage/user-id/2351487"&gt;@kristof_desaegera89d83&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is a known limitation in Fiori Elements OData V4. Validation messages targeted at a collection-valued association (_PackItems) are not automatically propagated to the generated sap.ui.mdc.MultiValueField&lt;/P&gt;&lt;P&gt;try,&lt;/P&gt;&lt;P&gt;Report the validation against a specific child field (e.g., PackItems-PackType) instead of the association.&lt;BR /&gt;If the error is at least one entry required use a parent-level message (page/object level)&lt;BR /&gt;Automatic red highlighting of MultiValueField for association-targeted RAP messages is generally not supported in current SAPUI5/Fiori Elements versions&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Sravan&lt;/P&gt;</description>
      <pubDate>Wed, 04 Nov 2026 08:41:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/rap-validation-message-targeting-a-composition-association-does-not/qaa-p/14516088#M4950993</guid>
      <dc:creator>sravan_aleshwaram</dc:creator>
      <dc:date>2026-11-04T08:41:14Z</dc:date>
    </item>
    <item>
      <title>Re: RAP validation message targeting a composition associ...</title>
      <link>https://community.sap.com/t5/technology-q-a/rap-validation-message-targeting-a-composition-association-does-not/qaa-p/14516118#M4950998</link>
      <description>&lt;P&gt;Hey Sravan, thank you for your response.&lt;/P&gt;&lt;P&gt;I was already thinking in this direction, but posted to verify.&amp;nbsp; For now, I put the message indeed on the parent element, showing a popup.&amp;nbsp; Still it's a bit confusing for the user to see all input fields in red, and the multivalue one not.&lt;/P&gt;&lt;P&gt;I did however already write some custom code that could filter out the specific message, and find the binded element myself.&lt;/P&gt;&lt;P&gt;This way I could set the UI element validation myself.&lt;/P&gt;&lt;P&gt;I did have some issues on resetting the validation when a user enters new data. Do you have any tips on resetting the state using oData v4 binding?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Nov 2026 09:26:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/rap-validation-message-targeting-a-composition-association-does-not/qaa-p/14516118#M4950998</guid>
      <dc:creator>kristof_desaegera89d83</dc:creator>
      <dc:date>2026-11-04T09:26:36Z</dc:date>
    </item>
  </channel>
</rss>

