|
I have 2 views. The only difference between the two, that I can tell, is that one of the views has a timerange picker around it's saved search. Here's the skinny
That code makes the "Schedule for PDF delivery" grayed out. My other view removed the TimeRangePicker and the 2 params after it and it's PDF delivery is not grayed out. Is it the case that the TimeRangePicker is causing the PDF delivery menu item to be grayed out? Or is there something else I should be looking at. Edit After taking Nick's suggestions to heart, I modified the XML to clean up the cruft. Still no luck with the "Schedule for PDF delivery" though, so here's the whole view.
|
|
2 things affect whether the 'Enable for PDF Delivery' option is available. 1) the 'actionsMenuFilter' on the TitleBar module. if the value is set to any of 'search', 'dashboard', 'dashboard-SimpleDashboard', then the link will show. I dont think this is your problem because I think it literally hides the menu option rather than simply greying it out. Worth double checking though. 2) whether or not the view contains an 'autoRun="True"' attribute. If it thinks that the view does NOT have one, then it will indeed disable the link. (when the pdfserver loads the view, there is no user to start things moving, so it requires at least one autoRun somewhere) I'm a bit confused because of course your view does contain an autoRun="True". Maybe if you post the whole view we can see what the deal is. UPDATE: taking a look at your full view posted in your update, I've figured it out. Apparently there's a bug in the python that goes and looks for autoRun attributes. It only looks at the top level modules. So move at least one of the autoRun="True" attributes up a level to a TimeRangePicker module and it'll start working. Note: I know you didnt ask about this, but a bunch of lines in your XML are only there because they get carried over when you convert from the Simplified XML. If you're in the advanced XML to stay, it can make things easier to read if you remove this cruft.
here's the result of these changes. You can see it's not a big difference but it's significantly less nested:
I wish I had my own little Nick here on my desk that I could ask splunk questions to. Thanks a TON for all those clarifications. Still no luck with the PDF link, so I've pasted the full view that I have. As you guessed, it was originally based off of a simple dashboard that was exported to advanced XML.
(21 Feb '11, 15:08)
caphrim007
Looks like there is a bug in the Python where it only checks top level modules for autoRun="True". Kind of lame but easy to workaround. See updated text above.
(21 Feb '11, 21:11)
nick ♦
Awesome. That did the trick. Thanks Nick!
(23 Feb '11, 18:36)
caphrim007
|
