cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Url Iview - Automatic Height problem

Former Member
0 Likes
453

I'm having a problem using the automatic height option with a Url Iview. It seems that the only way this option works is when the Url for the iview points to the same domain as the user's browser--in this case, since the browser is pointing at the portal instance this means that the url has to be pointing back to the portal server in order for the automatic height to work.

I believe this is a javascript security restriction when trying to resize the iframe on a different domain. I've scanned SDN documentation for any references, and found the following suggestion referring to iViews made from BW templates:

<b>"</b> <i>The automatic height function will not work because there is no domain resolvment done in that case (The BW Reporting Agent is not portal aware) and therefore the browser is not able to access the iframe for changing its size.

However it will work if you add javascript for resolving the domain to their web template.

<script language="Javascript">

var lsDomain = "";

var liBehindFirstDot = location.hostname.indexOf( "." ) + 1;

if (liBehindFirstDot > 0) document.domain = location.hostname.substr( liBehindFirstDot );

</script></i><b> "</b>

Could this approach work for my Url Iview issue? Can I make a new template from the current Url Iview template (so not to affect the default Url Iview template)?

Any help or suggestions would be appreciated.

Thanks,

Curt

View Entire Topic
Former Member
0 Likes

Hello Detlev,

I hope you still watch this topic!

I have a similiar problem: I want to use the automatic height with url iviews pointing to pages on the same server and if possible avoid to add the JS to every page.

If I understood this right, the problem in my case is, that the portal relaxes it's domain let's say from server.sub.top.de to sub.top.de and the HTML-Pages are still on server.sub.top.de.

Is it possible to keep the portal from relaxing it's domain completeley or for one page? Then both would be on same domain again and the portal could access the pages's properties.

Thanks and Greetings,

Reinhard