# PDF template developer

**URL:** <https://community.fibery.io/t/pdf-template-developer/7725>\
**Category:** Get Help\
**Created:** [November 1, 2024, 6:01pm UTC](https://community.fibery.io/t/pdf-template-developer/7725 "2024-11-01T18:01:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jpajot](https://avatars.discourse-cdn.com/v4/letter/j/22d042/32.png) [@jpajot](https://community.fibery.io/u/jpajot)\
**Post date:** [November 1, 2024, 6:01pm UTC](https://community.fibery.io/t/pdf-template-developer/7725/1 "2024-11-01T18:01:47Z")

</div>

Ho there, I’m looking for a PDF Template Developer well versed in the universe of Fibery. Especially, if it is even possible, to explore the use of View of an entity **as a parameter to dynamically send fields to the template** , instead of having to specify every fields for each template. So 1 PDF template could be much more versatile from entity to entity.

Any candidate or insights on the matter?

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [November 1, 2024, 7:10pm UTC](https://community.fibery.io/t/pdf-template-developer/7725/2 "2024-11-01T19:10:03Z")

</div>

Can you clarify what your expectations are.  
Do you want a PDF template that will be usable for any entity, no matter the fields in the respective databases?

---

<div class="post-metadata">

**Author:** ![jpajot](https://avatars.discourse-cdn.com/v4/letter/j/22d042/32.png) [@jpajot](https://community.fibery.io/u/jpajot)\
**Post date:** [November 2, 2024, 7:30am UTC](https://community.fibery.io/t/pdf-template-developer/7725/3 "2024-11-02T07:30:16Z")

</div>

Sure, let’s start with a PDF template for any entity within 1 DBB so the comolete set of fields is known and fixed. 1 entity can have multiple views depending user needs. When clicking the standard button action to generate PDF using template, I’d like for the template to receive the current view OR ask user to select the view of the entity he wants to use for printing. This way a single template per DBB is flexible enough. Imagine I add a field to the DBB, thanks to this I don’t need to go in every PDF template to add this field, I just uodate my views accordingly et voilà. (I used this - with a developper since I’m inept in scripting these things - with Microsoft Reporting Services and an Oracle DBB, worked like a charm).

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [November 2, 2024, 8:15am UTC](https://community.fibery.io/t/pdf-template-developer/7725/4 "2024-11-02T08:15:19Z")

</div>

> [@jpajot](#):
>
> When clicking the standard button action to generate PDF using template, I’d like for the template to receive the current view

PDF generation in an automation happens on the backend, and it doesn’t know anything about what view(s) you (or any other user) might have open, so it’s not possible I’m afraid.

---

<div class="post-metadata">

**Author:** ![jpajot](https://avatars.discourse-cdn.com/v4/letter/j/22d042/32.png) [@jpajot](https://community.fibery.io/u/jpajot)\
**Post date:** [November 2, 2024, 7:00pm UTC](https://community.fibery.io/t/pdf-template-developer/7725/5 "2024-11-02T19:00:08Z")

</div>

Understood. Side question, any plan to have a module for integrated PDF Templates Editor?