Allow using a view as data source

Hi there,

would also really be interested to use tokens from two diffrent nodes.

e.g. a user signs up an chooses a particulary node, the user information stored as cck as well as the information regarding the choosen node should be handed to the PDF.

Any help would be really appreciated.

Great module !

Thx

Christian

The >1nid (or multiple token-sources in general) problem is definitely on my TODO. This shouldn't be difficult to develop, and was in fact what I was originally intending, but got sidetracked .

When I get that puppy going, pulling en entire view in as one field would be easy via token_custom, but I'm not sure about linking a Form to a view to map view-fields to form-fields. Initial impression is that this will be difficult, and will be towards the bottom of my list. If the >1nid fix sheds light as to the contrary, I'll keep you posted.

Sounds great!
thanks for the fast reply!

Alright, I'm separating this out into two tickets: views integration, and multiple Nodes. Added the multiple node functionality! see #708796: Multiple node sources for how-to

This is an interesting request. Is anyone still interested in this? I think it can all be done with what we have right now myself...since Views are usually made up of nodes anyway, or the two can be tied together in various ways.

New features will happen for 7.x now, so bumping version.

From what I have read and tried there is no way now to actually populate a pdf with a user's data. A feature likes this would be amazing addition to this amazing module.

What I want to know if there is a workaround I could implement. Like using a view with an uid argument to create the data and then save them elsewhere in the site so Fill PDF can get them. The #7 comment got me thinking but I cannot figure out how using views and rules I could achieve this. Any insights anyone?

perisdr: This is a bit late in the game, but you can use chained Node or Webform tokens to get user information. So if the user owns a node, you could fill with stuff like node:author:(token). If you expand the token help, these are there.

Could it also possible to generate a PDF from a views?
I try to serve a views page as PDF (download)...

JohnnyX: Check Views PDF.

Tested, but doesn't working because of a bug. Waiting for a fix.

Thanks

#1606828: Expose FillPDF metadata to Views has some discussion around this too. This one will likely be solved when Fill PDF Fields are developed, but leaving it open and postponed until the issues regarding Fill PDF Fields in Views and views of Fill PDF Configurations are distinct and clear (right now they're all kind of running together).

Tagging also.

Will be looking at this interesting and IMO important feature request.

While chained tokens cover a number of usecases, using a view as our single source would allow us to completely deprecate populating a single FillPDF form with n entities. Instead we would allow either one entity or one view as our data source.

Complex entities with a number of 1:1 and/or 1:n relations wouldn't require replicating the logic anymore, if all fields are present in a single, flat (and possibly aggregated) view.

This would also simplify #1517652: [PP-1] Increase redirectability of Fill PDF URLs.