New Topic

Category Report Builder

Product Version 8.0

Displaying drill report in embedded mode

Maja Belobaba shared this idea ago

Completed

Hi,

Is it possible to make a drill report able to open in a new window/tab/page in embedded mode? Or to "overwrite" the dashboard and show only the drill report on a current page?

That is how a drill report will open directly in Yellowfin, but when a dashboard is embedded, the drill report will open in the existing report's box on the landing dashboard.

Also, there is a "Pop Out window" option in the drill report settings but it is not working the same way in Yellowfin directly and in embedded mode.

Regards,

Maja

I like this idea 0

Replies (16)

Mike Sheehan ●

Hi Maja,

Thanks for reaching out. I can see that clicking a drill through hyperlink in YF directly takes you to the report itself (instead of staying in the same window), but I'm actually not able to open the drill through in my dashboard at all though. Would it be possible to supply the script you're using to load your Dashboard?

Regards,

Mike

Reply URL

Maja Belobaba ●

Hi Mike,

Thank you for helping!

It's just the way how drill though is working in embedded mode. Try to embed the dashboard.

Do you need embed link or you meant on something else?

Kind regards,

Maja

Reply URL

Mike Sheehan ●

Hi Maja,

The reason I ask is because there could be differences in behavior when using JSAPI v3 vs. v2, for example. Another difference could be in different versions. I can see the type of behavior you're describing in v2, so I'm assuming you're using v2:

/ce8ef925a55353767bc3177709e1ad6c

/729311900340a445dc4dada0e8b4a35d

This is what reports on a dashboard embedded via JS API v3 looks like instead:

/ffe3cc0f176024698210550cbd406731

The JS API v2 is officially considered legacy at this point so this functionality won't be changed. That said, Drill Through with pop-up window is an existing enhancement for the JS API v3, but it doesn't exist yet.

You can reference our Wiki for differences between v3 and v2 of the JS API, if curious. The v3 version is more robust, and better looking. That said, we're waiting on the Drill Through functionality in v3, so if you need this functionality, you may not be ready to use the v3 API instead of v2 as of yet.

Anyways, I can set this to Enhancement Logged should you be interested in utilizing v3 in the future, so I can let you know when this is developed and published in a build. Please let me know.

Regards,

Mike

Reply URL

Maja Belobaba ●

Hey Mike,

Thanks for the explanation!

This is an example of our embed link:

Is there any way we can open a drill report in a new window?

Thanks,

Maja

Reply URL

Mike Sheehan ●

Hi Maja,

Thanks for your response. Your script is using the v2 JS API. As stated in my previous response, this isn't possible in v2, but will be soon in v3. I've set this to Enhancement Logged to let you know when this feature has been developed out and will let you know when said build arrives and what if anything would need to be added to your script to make this possible.

Regards,

Mike

Reply URL

Maja Belobaba ●

Hi Mike,

I'm opening the ticket again to ask you is there a way to open a drill report in a new window if we add some additional command in the CSS? Something like target=new?

Kind regards,

Maja

Reply URL

Mike Sheehan ●

Hi Maja,

Thanks for reaching back out. I think that 'target=new' could work in several contexts, but I'm unsure how this would be able to be applied specifically to the hyperlinks found on drill reports.

It may be possible to accomplish this for all hyperlinks on a page though. This thread here indicates three separate methods for accomplishing this via HTML, jQuery or JavaScript.

Regards,

Mike

Reply URL

Mike Sheehan ●

Hi all,

Just writing to let you know that 9.4, which contains this enhancement, has now been published. You can download the full installer here.

Here are the direct links to download the update installers: .exe / .jar

Please download and install and confirm the fix when you get the chance.

Regards,

Mike

Reply URL

Maja Belobaba ●

Hi Mike,

Thanks for your update.

We made an upgrade to 9.4 to check functionalities and unfortunately, I'm not able to test anything in embed mode because I'm getting the blank page. If I remove "v3?" part from the embed link then my dashboard displaying but without filters and drill reports are not opening in a new window.

Are you familiar with this issue? Is there any way how to fix it?

Thank you,

Maja

Reply URL

Mike Sheehan ●

Hi Maja,

This is the entire script I'm using for testing and it works as expected:

<!DOCTYPE html>
<html>
<head>
	<style></style>
	<meta charset="utf-8"/>
</head>
<body>
<script type="text/javascript" src="http://localhost:9494/JsAPI/v3?dashUUID=f20c11a1-4aa3-4a2c-925a-209ba032558f"></script>
</body>
</html>

If you open your F12 Browser Console, what do you see there? If you see a string of weird looking characters, there's an encoding issue, and you have to specify the charset as I've done above. If it's something else, please send a screenshot of what it is so we can determine next steps.

Regards,

Mike

Hi Maja,

This is the entire script I'm using for testing and it works as expected:

<!DOCTYPE html>
<html>
<head>
	<style></style>
	<meta charset="utf-8"/>
</head>
<body>
<script type="text/javascript" src="http://localhost:9494/JsAPI/v3?dashUUID=f20c11a1-4aa3-4a2c-925a-209ba032558f"></script>
</body>
</html>

Regards,

Mike

Reply URL

Maja Belobaba ●

Mike,

The encoding issue is resolved with your script, thank you. But I'm still having one. The port number should be 9494? I'm not on my territory with this, sorry :)

Regards,

Maja

Reply URL

Mike Sheehan ●

Hi Maja,

Glad to hear adding the encoding information worked! The port number should be whatever number your Yellowfin instance is on. The default port is 8080. I just have multiple instances installed, so I made my 9.4 install's port 9494 to make it easier to remember which instance is which, haha.

Please let me know if you have any other questions or concerns.

Regards,

Mike

Reply URL

Maja Belobaba ●

A-ok then :)

So this is my script:

/fd415a74d61e7015419c05d2fc7b30eb

And this is what I'm getting after opening HTML in browser:

/85db0d2713bca055f84209f5784cd6f4

Do you have an idea what is the problem here?

Regards,

Maja

Reply URL

Mike Sheehan ●

Hi Maja,

It sounds like you may be missing the Allowed Origins settings. You can find more about this here: How do I start using the JavaScript API v3?

If this still doesn't work, the only other possibility I can think of is perhaps you're not trying to reach the API from the Yellowfin ROOT path. For instance, trying to reach the API using a JSP page in your desktop wouldn't work.

Please check these settings and let me know how goes.

Regards,

Mike

Reply URL

Maja Belobaba ●

Good morning Mike!

What should I add for Allowed Origins if I want to test embedded mode locally for now?

Reply URL

Mike Sheehan ●

Hi Maja,

It should be whatever URL(s) you are accessing the site from. 'https://172.24.216.6:8443' would likely be at least one of those values based on the screenshot you provided.

Considering this is a public Idea item that's been implemented, if you're still struggling with this after my latest response, please open a separate ticket and we can continue from there.

Regards,

Mike

Reply URL