<?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>topic Re: View cluster : dynamic fields on navigation in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/view-cluster-dynamic-fields-on-navigation/m-p/12726711#M2020171</link>
    <description>&lt;P&gt;It depends what means "the structure in folder 2". I don't get it.&lt;/P&gt;&lt;P&gt;You have a few events (user exits) for View Clusters that you can implement.&lt;/P&gt;&lt;P&gt;Usually, if you have different information, you create several tables at level 2.&lt;/P&gt;</description>
    <pubDate>Fri, 09 Dec 2022 14:05:42 GMT</pubDate>
    <dc:creator>Sandra_Rossi</dc:creator>
    <dc:date>2022-12-09T14:05:42Z</dc:date>
    <item>
      <title>View cluster : dynamic fields on navigation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/view-cluster-dynamic-fields-on-navigation/m-p/12726710#M2020170</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;
  &lt;P&gt; Is it possible that we display dynamic table/structure in a View cluster on navigation, based on the entry selected in the first table control.?&lt;/P&gt;
  &lt;P&gt;Example : The structure in Folder 2 will vary based on whether the user selects '01' , '02' , '03' or '04'. &lt;/P&gt;
  &lt;P&gt;Is this feasible? if so, any leads on how his can be achieved? &lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2117757-image.png" /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Dec 2022 07:17:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/view-cluster-dynamic-fields-on-navigation/m-p/12726710#M2020170</guid>
      <dc:creator>former_member206377</dc:creator>
      <dc:date>2022-12-09T07:17:37Z</dc:date>
    </item>
    <item>
      <title>Re: View cluster : dynamic fields on navigation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/view-cluster-dynamic-fields-on-navigation/m-p/12726711#M2020171</link>
      <description>&lt;P&gt;It depends what means "the structure in folder 2". I don't get it.&lt;/P&gt;&lt;P&gt;You have a few events (user exits) for View Clusters that you can implement.&lt;/P&gt;&lt;P&gt;Usually, if you have different information, you create several tables at level 2.&lt;/P&gt;</description>
      <pubDate>Fri, 09 Dec 2022 14:05:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/view-cluster-dynamic-fields-on-navigation/m-p/12726711#M2020171</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2022-12-09T14:05:42Z</dc:date>
    </item>
    <item>
      <title>Re: View cluster : dynamic fields on navigation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/view-cluster-dynamic-fields-on-navigation/m-p/12726712#M2020172</link>
      <description>&lt;P&gt;Thanks for your reply, here's what I mean by  structure in folder 2 :&lt;/P&gt;&lt;P&gt;When you see in the screenshot that I have attached along with the question, If the user selects the row '01' and selects 'Folder 2' there would be a different table available for EDIT when compared to '02' . '03' or '04'. &lt;/P&gt;&lt;P&gt;1. For example, this are fields that should be for Edit, on selection of '01' in screenshot 1.&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2117817-image.png" /&gt;&lt;/P&gt;&lt;P&gt;2. This is the structure to be made available for Edit on selection of '02'.&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2117818-image.png" /&gt;&lt;/P&gt;&lt;P&gt;so the table is dynamic here as you can notice, This is the requirement. &lt;/P&gt;&lt;P&gt;I am checking for event 03 but unsure which structure needs to be modified. &lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2022 07:34:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/view-cluster-dynamic-fields-on-navigation/m-p/12726712#M2020172</guid>
      <dc:creator>former_member206377</dc:creator>
      <dc:date>2022-12-12T07:34:26Z</dc:date>
    </item>
    <item>
      <title>Re: View cluster : dynamic fields on navigation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/view-cluster-dynamic-fields-on-navigation/m-p/12726713#M2020173</link>
      <description>&lt;P&gt;I think you cannot do it in a true "dynamic" way (at least with reasonable effort), but you can make a few things that will make your viewcluster behave as if it was such (more or less).&lt;/P&gt;&lt;P&gt;First thing to note is the definition of a viewcluster is static. In SE54 you define its structure: the top most table/view and the entire hierarchy of its subtables/subviews.&lt;/P&gt;&lt;P&gt;So if you want any subtable/subview to appear in a viewcluster screen for a user, each such subtable/subview should be defined in a viewcluster deinition (SE54) as an element of the viewcluster hierarchy. &lt;/P&gt;&lt;P&gt;What you can do - if you don't want all of these subtables/subviews to be always available for a user - is to:&lt;/P&gt;&lt;P&gt;a. Forbid navigation to a specific subtable/subview - based on some conditions;&lt;/P&gt;&lt;P&gt;b. Hide a specific subtable/subview entry in a viewcluster tree panel.&lt;/P&gt;&lt;P&gt;Ad. a.: "forbid navigation" means to reject user's action (possibly display some message too) when the user double clicks on a specific subtable/subview entry in a viewcluster tree - an entry that is not suuposed to be used in context of values present in record selected in the main table/view. You can do it with viewcluster event 03 ("Before Calling View Maint Module for a Subdialog").&lt;/P&gt;&lt;P&gt;Ad. b.: You can make some of entries invisible in a viewcluster tree (by setting VCL_STRUC_TAB-SUPPRESS = 'X') based on some conditions - but I have not tested this within event 03 so not sure if it works there (I used it only with event 02 "After Getting the Database Access Select Conditions").&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;</description>
      <pubDate>Wed, 21 Dec 2022 14:40:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/view-cluster-dynamic-fields-on-navigation/m-p/12726713#M2020173</guid>
      <dc:creator>Maciej_DomagaBa</dc:creator>
      <dc:date>2022-12-21T14:40:30Z</dc:date>
    </item>
    <item>
      <title>Re: View cluster : dynamic fields on navigation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/view-cluster-dynamic-fields-on-navigation/m-p/12726714#M2020174</link>
      <description>&lt;P&gt;Hello Maciej,&lt;/P&gt;&lt;P&gt;                  Thanks for your inputs. I would like to try the option Ad.(b) as suggested by you. &lt;/P&gt;&lt;P&gt;For now, I have found a solution by hiding fields which were not necessary and displaying only those which were necessary. I have written this in the PBO event of TMG. This solved my problem for now. However, I will try adapting (b) point of your suggestion&lt;STRONG&gt; (&lt;/STRONG&gt;&lt;STRONG&gt;by setting VCL_STRUC_TAB-SUPPRESS = 'X). &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Thu, 22 Dec 2022 04:41:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/view-cluster-dynamic-fields-on-navigation/m-p/12726714#M2020174</guid>
      <dc:creator>former_member206377</dc:creator>
      <dc:date>2022-12-22T04:41:52Z</dc:date>
    </item>
  </channel>
</rss>

