-
1. Re: Web tab configuration - sub entity display
Kiran Ruhil Dec 14, 2018 3:42 AM (in response to Kiran Ruhil)Hi All,
Any help on this topic will be very much appreciated. For now, we can see possible soultion is to remove the field available above the table and have that field in some other tab.
If anyone has better idea or a solution to this problem, kindly let me know.
Regards,
Kiran
-
2. Re: Web tab configuration - sub entity display
Stefan Reinhardt Jan 3, 2019 6:36 AM (in response to Kiran Ruhil)Hi Kiran,
though I may not have a direct answer I was still wondering if this could be related to Re: Unable to view complete data of a product at SubEntity tab ?? Does it sound similar to you?
Stefan
-
3. Re: Web tab configuration - sub entity display
Kiran Ruhil Jan 3, 2019 3:26 PM (in response to Stefan Reinhardt)Hi Stefan,
Yes, It's the same issue ( Re: Unable to view complete data of a product at SubEntity tab) faced within our Team. We have raised this as a case with Informatica support and R&D Team is looking into this.
We have been provided with the JIRA "HPM-43907 : Scrollbar disappears in web client". Issue is purely because of scroll bar in web configuration.
Below are more details to this issue.
Regards,
Kiran
-
4. Re: Web tab configuration - sub entity display
Stefan Reinhardt Jan 4, 2019 2:55 AM (in response to Kiran Ruhil)Thanks for the update Kiran. Ugh, nasty that it is in fact the scrollbar and not the data load that causes the issue here :-( I am aware of that ticket and will have a close look at it as well hoping for a fix in a short time frame.
Best,
Stefan
-
5. Re: Web tab configuration - sub entity display
Kiran Ruhil Aug 14, 2019 8:34 AM (in response to Kiran Ruhil)Thanks to Informatica support Team, With 8.1.1.02, this issue is solved.
Detail Tab customization
Starting with this version, in case a custom detail tab has a combination of fieldGroup and tableGroup, then a fetchSize attribute needs to be mentioned in the tableDefinition which helps in identifying the page length of the defined table. This will allow the table to grow and show records, maximum up to the defined fetchSize number. The fetchSize defined for the table should roughly match the number of records expected to be fetched.
Below is an example of detail tab having tableDefinition with fetchSize set to 200. In this case the page length of the defined table will be at the maximum 200 records.
<definition debugId="example" i18NKey="example" position="191" rootEntity="Article" >
<column>
<fieldGroup displaySectionWidget="true" subEntityId="ArticleLang">
<field identifier="ArticleLang.DescriptionShort" />
</fieldGroup>
<tableGroup>
<tableDefinition rootEntity="ArticleReference" fetchSize="200">
...
</tableDefinition>
</tableGroup>
</column>
</definition>