Question

Looker 6.6 PDF Visualization Errors

  • 20 February 2019
  • 44 replies
  • 971 views

Hi Looker,


We recently updated to 6.6 (Looker hosted instance) and we’re encountering some visualization issues when downloading to PDF. For example, this is what we see on the dashboard:


06%20PM


These are the same tiles downloaded as a PDF with “Fit Page to Dashboard” selected:



I’ve tried selecting “expand tables” and a few different paper size options, but am still seeing formatting errors. Any suggestions?


Thanks,


44 replies

Userlevel 7
Badge +1

Thanks for the excellent detail, context, and the suggestions on how to approach a fix. All three of those are extremely useful, and I’ll get this in front of those working on it.


There’s a lot in there, so I’m going to focus on the 800px cut off for now, but your other considerations are all greatly appreciated and understood— I will look into them as well.


I’ll be keeping this thread updated and as always, keep firing away with any questions.

Userlevel 6
Badge

I have just notice that the legacy rendering feature is still available until 6.10 (which says for some reason is in about 18 days, 6.8 i would assume is actually in that time). I thought I had read that it was gone in 6.6 but I never took a look in the legacy features section in admin.

I am thinking about turning this back on and testing, unfortunately this is bad timing for us as our dev instance is broken!

Userlevel 7
Badge +1

Good to know!



I suppose that is what dev instances are for.


Daily update: I passed along your suggestions @nicolaipj, and I know our engineers also went back to older versions to look at how we did this kind of rendering previously. We have identified a working fix for the column cut-off issue, and are hoping to finalize it very soon. More to come shortly.

Userlevel 7
Badge +1

It’s been a couple of days— Our latest fix is complete and is just going through testing. Once it’s out, I’ll let you all know and you can download the new jar file.


Have a nice weekend! Let me know if there’s any questions, and I’ll update here as soon as I know more.

New security update 6.6.21 has this bug fixed already or should we wait until new version comes out?

Userlevel 6
Badge

Is there an update on this today please?

+1 It would be great to get an update on this, it has been nearly a month now and would be great to arrive at the full resolution

Userlevel 7
Badge +1

I have my fingers crossed that it will be available soon, but there’s no update yet— We’re still running tests. I’m working with the engineers on this one and I’ll know as soon as it’s available. Thanks for your patience, and know that I’ll be filling you in the second I have news.

We have recently upgraded to the latest version of Looker 6.6.17 and seeing this error for our scheduled reports for most of the users “format format wysiwyg_pdf invalid – valid formats for Dashboard sent as ‘email’ are [:csv_zip] (code: invalid)”


Just want to confirm that this is the related to the same mentioned in this thread. What you guys recommend to do here, wait for update or turn on the Legacy feature “Legacy rendering on” until we get a fix for this ?

Userlevel 6
Badge

Hi Izzy, this is getting a bit desperate for us. Can you please spend a small amount of time looking into if 6.6 has directory and/or db schema changes from 6.4. I am looking at putting the old jar back. I will have a test as well by turning on the legacy rendering.

Userlevel 7
Badge +1

Definitely, I’ll verify whether 6.4 & 6.6’s schema are compatible in the morning when those in the know wake up.


In the meantime, let me know if legacy rendering works, and I’m also quite confident that we will have a working jar for you tomorrow as all tests on the fix have passed.

Userlevel 7
Badge +1

@IanT, there were changes to the schema between 6.4 and 6.6 that make a rollback a bad option (There almost always will be problems between versions). I definitely can’t recommend replacing the jar.


I’m working for availability of the fix today. Would you be open to updating to a version of 6.8 that would contain the fix, or would you prefer to stay on 6.6 and patch that?


I also took a few minutes to run some tests and it looks like Legacy Rendering is working well (ie: not cutting off columns) so I definitely recommend turning that on and proceeding with your schedules for now.

Userlevel 6
Badge

Yes I turned this on today in dev (got it working after a while!) and it was back to the good old days, I will turn this on in production and can test 6.6 with the hopeful fixes. In light of this issue from now on we will be upgrading versions with a longer lag time so we can fully test versions (6.8) and see issues from other customers before we encounter them ourselves 😉

Userlevel 7
Badge +1

Noted, I’ll take that to answer my question— in favor of a patch for 6.6 and not just an updated 6.8. Thanks for letting me know, I’ll run that back and get it built.

Userlevel 7
Badge +1

Hi everyone, some good news today— The updated fix has been completed and released!


I know most of you are still on Looker 6.6, so if you want an updated version of 6.6 that just includes the visualization updates, follow the normal jar download procedure but select “Specific Version” and enter looker-6.6.22.jar.


If you have updated to 6.8, you can do the same thing but enter looker-f9eabe4492a-6.8.11.jar.


@dgold, or anyone else in the thread that is Looker-hosted, I think the best course of action would be to reach out to support to get updated— Either via chat or help.looker.com.


Let me know how that works for your renders! Happy to field any feedback, and would also love to hear if all is working well.

Hi Izzy,


Thanks for the update. Does this also have the security update released earlier this week?

Userlevel 6
Badge

can you double check the name of this, am failing to find this via api or website.

thanks


edit: just tested 6.8.12 and it seems to have resolved our cropping issues.

Userlevel 7
Badge +1

6.8.12 was just built yesterday, so that also contains the fix, yep— It’s also just the looker-latest.jar at this point so unless you’re interested in remaining on 6.6, you don’t need to worry about the special names.


I’m thrilled to hear that resolves your issue. Thanks again for your patience and for your and @nicolaipj’s ideas & feedback. I haven’t forgotten about your “Other Considerations”, Nicolai!

Userlevel 7
Badge +1

Yes it does.

Reply