Thanks Victor, that sounds like a good idea. I will look up user ids and see what I can find in the documentation. Do you happen to know where there is any instructions for this? Either displaying the pdf in the client view or links is both acceptable.
Thanks Victor, that sounds like a good idea. I will look up user ids and see what I can find in the documentation. Do you happen to know where there is any instructions for this? Either displaying the pdf in the client view or links is both acceptable.
To utilize user IDs, the pre-requisite is that the user is registered in WordPress. WordPress controls user id assignment. Formidable's User Registration add-on can be used to facilitate the process.
The user id field stores the user's ID when they fill in a form. See this: https://formidableforms.com/knowledgebase/user-id/
If both forms have the same user id, they can be linked for whatever purpose you design. You should make sure you are allowing 1 entry per user otherwise it gets a little more complicated because you have deal with entry ids as well.
[e2pdf-view id="1" dataset="[id]"]Where "1" is the id number of your certificate template and leave the dataset [id] as-is; that's the dynamic ID of the individual client profile. You could use nested views, if need be. With FF's recent PDF enhancements, you might not need E2PDF any longer, and keep it all native to Formidable. One thing I've found where E@PDF excels: placing Formidable fields with pixel-level precision. That's something that currently takes quite a bit of effort using Formidable Views. Hope this helps :)
Please login or Register to submit your answer