-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filtering does not work for a full workbook (--fullpdf) #233
Comments
Noting the same issue |
Filtering is also not working for single dashboard export. I thought this had been resolved. Code sample below. tabcmd export "MyDashboard/Overview?Local%%20Number=123456" --pagelayout landscape --pagesize letter --pdf --filename "\MyLocalServer\Facebook\FB PDF Reports\123456-MAR 2023-Facebook Report.pdf" I've tried it with "%%20" and "%20" and neither are working. I'll try with no space to see if that works. |
Having no space in the filter name "DealerNumber" is working for a SINGLE dashboard export. |
Hi All, Basically, we won't be able to print a pdf file with multiple pages and a filter until this issue is resolved, right? Thanks in advance. Regards, |
Any update on this issue affecting filtering --fullpdf exports, or any known workarounds aside from splitting the views into separate PDFs? The issue still persists in v2.0.11. Thank you. |
This is a HUGE problem. I generate monthly billing statements for 50k+ users via TabCmd. Any updates? |
I can confirm the same issue. Very frustrating to force tabcmd 2.0 and not even have the same level of functionality. No communication on a potential fix either. |
Well. Here we are 3 months later and the issue still persists. Is anyone at their desk? |
FYI below is the response I got after opening a support case. We have moved away from TabCMD due to this issue, and are instead calling the Query View PDF endpoint from Python.
|
That's a somewhat confused response from support and I will follow up to make sure they understand that they do, in fact, offer support on both versions of tabcmd. However, they are correct that the missing piece here is functionality on the server. There is no code update to Tabcmd 2 that will make workbook filtering work, it needs to be shipped in an update to server. I don't know a timeline of when that will happen. A couple notes
|
yikes. that is wild. to suggest using "original tabcmd" and then forcing the update for MFA is just piss poor support. I will say my rep was better at least. it took them over a week to simply confirm it is a known issue with no comment on when a fix will be in. this was roughly three weeks ago. |
I have made a workaround Python script to do this, which you can download here. Feedback welcome! https://github.com/TheInformationLab/tableau-tools/tree/main/tableau-server-pdf-downloader |
This is a huge issue for us as well. Bulk exporting PDFs takes hours when you have to connect to the server for each individual view/PDF. Is there an update on when this functionality will be added? How can we revert to original tabcmd in the meantime? |
I do not believe it has been fixed yet. You could likely download the previous tabcmd version and then attempt to reference it instead of the 2.0 one. We simply chose not to because we had already updated all references and syntax changes. also, I believe we were forced into using 2.0 due to the security changes that were pushed around 2.0 launch. |
I don't think it's possible for us to use the original tabcmd, as we use Tableau Cloud (not Tableau Server). |
There is a way to authenticate with tabcmd 2.0 using PAT and then use the authentication token received with tabcmd 1.0. I can't quite recall the details but I think you can get an auth token from using tabcmd 2.0 and then it's just a case of copying that auth token into a file in the tabcmd 1.0 directory structure somewhere. Sorry for being so vague but it might be worth investigating this approach if it's critical! |
With the news that tabcmd v1 will be retired for all users pending the move of Tableau Cloud to Hyperforce in October/November, I am hoping this (and other parity issues) are resolved before then, or it will cause quite a few breaking changes to lots of customer workloads. I can see the in-progress tag was added on May 10, but is there any further news on this @jacalata? |
Filtering the data in a viz for export only works when exporting a single view at a time.
tabcmd export /WorldIndicators/Population --pdf -f b1.pdf --filter "Birth Rate Bin=1.5-3%"
#176 (comment)_
The text was updated successfully, but these errors were encountered: