Settings and activity
18 results found
-
34 votes
Hi Pandas,
I'm Alex, the Product Leader for the Integration Ecosystem at PandaDoc.
I wanted to update you that we are actively considering the development of custom object mapping, which would allow you to connect your custom objects to PandaDoc’s data model for both retrieving and syncing information.
Given that custom objects can be complex, we want to ensure we fully meet your requirements before moving forward. I've flagged this item on our roadmap, but I’d love to discuss it further with you to ensure we’re aligned on expectations.
Please feel free to schedule a time with me here:
https://calendar.app.google/pHa6Xud82oexdoyv6
Looking forward to our conversation!
Thanks, Alex
An error occurred while saving the comment 
Joseph Tenney
supported this idea
·
-
8 votesJoseph Tenney
supported this idea
·
-
17 votesJoseph Tenney
supported this idea
·
-
37 votes
Hi. We aren’t planning on building this into our feature set at this point in time since it doesn’t fit into our current product roadmap. Please keep upvoting this idea so we can keep considering it every time we work on our roadmap.
Should you come across any other ideas that suit your business needs, don’t hesitate to give them an upvote!
An error occurred while saving the comment Joseph Tenney
commented
Also would like to add, a way to pass a viable into the component to tell it which workspace its using. so for customers assigned to one account it would open to that work space, but for a customer assigned to another account it would open to that one.
Joseph Tenney
supported this idea
·
-
7 votesJoseph Tenney
supported this idea
·
-
17 votesJoseph Tenney
supported this idea
·
-
16 votesJoseph Tenney
supported this idea
·
-
7 votesJoseph Tenney
supported this idea
·
-
4 votesJoseph Tenney
supported this idea
·
-
21 votesJoseph Tenney
supported this idea
·
-
4 votesJoseph Tenney
supported this idea
·
-
17 votesJoseph Tenney
supported this idea
·
-
66 votes
The status of this suggestion is currently unchanged. Please check back for updates.
Joseph Tenney
supported this idea
·
-
5 votesJoseph Tenney
supported this idea
·
-
1 vote
An error occurred while saving the comment Joseph Tenney
commented
To be more specific this is referring to Fillable fields that can be assigned out. it's currently possible to add multiple variables in a standard text field, but the fillable field only allows for one crm field to be entered in the merge field.
Joseph Tenney
supported this idea
·
-
100 votes
Hi. We aren’t planning on building this into our feature set at this point in time since it doesn’t fit into our current product roadmap. Please keep upvoting this idea so we can keep considering it every time we work on our roadmap.
Should you come across any other ideas that suit your business needs, don’t hesitate to give them an upvote!
Joseph Tenney
supported this idea
·
-
129 votes
Great news! We're updating our platform to let you easily format data passed from your CRM right in PandaDoc. We're now working on a UX that will allow data formatting and normalization right on the UI (in addition to standard hardcoded rules on the backend). Stay tuned for a smoother, more intuitive experience!
Thanks for your suggestions – they're helping us make our platform better for everyone.
Joseph Tenney
supported this idea
·
-
292 votes
We wanted to share an update regarding the idea. After careful consideration and further analysis of the idea, we have adjusted its status to "Not Planned."
This change allows us to further explore the feasibility and impact of this and other requested enhancements, ensuring that any updates we introduce are in the best interest of our users and align with our platform's long-term vision.
We appreciate your understanding.
An error occurred while saving the comment Joseph Tenney
commented
This is a must. we get around it now by adding +1 just before the @ symbol. but this sometimes causes spam filters to quarantine the message so it makes delivery unreliable.
Joseph Tenney
supported this idea
·
.png){kind=link}
This is important as we use the contract object to store signed documents not Opportunities.