Api pricing table elucidation
Hello,
I am trying to create a pricing table via api.
there are few objects in the api structure that I cannot understand what they do. I am taking the below JSON from the help documentation:
"pricing_tables": [ { "name": "Pricing Table 1", "data_merge":true, "options": { "discount": { "type": "absolute", "name": "Discount", "value": 2.26 } }, "sections": [ { "title": "Sample Section", "default": true, "rows": [ { "options": { "optional": true, "optional_selected": true, "qty_editable": true }, "data": { "Name": "Toy Panda", "Description": "Fluffy!", "Price": 10, "QTY": 3, "SKU":"TEST1", "Tax": { "value": 7.5, "type": "percent" }, "CustomText":"testcolumn" }, "custom_fields": { "Fluffiness": "5 / 5" } } ] } ] } ]
First and foremost, the discount object. what does that do? how is the value 2.26 reflected in the table output from the document? From your help doc screenshot, i cannot see the 2.26 anywhere(see screenshot)
second, the title key (Sample section), does that add anything to the final output? As again I cannot see the sample section text anywhere. does it matter what the title i pass via API is since the sample section string is nowhere in the output document.
third, custom field object. what does this do? Especially, the fluffiness. What is that supposed to mean (5/5). When does this object need to be included in the JSON? for your example, how does the custom field fluffiness impact the output pricing table from your example (in the screenshot)?
fourth, I have opportunity products in SFDC that i will need to push to PandaDoc via api. The description field in my Opportunity products is a text field split in breaks with bullet points like the below :
-
Official comment
Hi there,
1. For the discount, it looks like the screenshot is incorrect. When you put a discount in the "options" section of the pricing table object it will apply a global discount to the table's summary:
2. The 'Sample' section will be the name of that section of the pricing table if you are passing more than one section. By default, when you add a pricing table to your template it does not have any sections, which that screenshot is reflecting. My screenshot above shows how it will look when you use multiple sections.
3. The custom field allows you to add a custom plain text column to your pricing table. "Fluffiness" is just an arbitrary value used in this example. You can also pass multiple custom columns:
"custom_fields": {
"Fluffiness": "5 / 5",
"test": "test value"
}
4. Yes, in the description for the line item you can html to keep the bulleted list using either of the following syntax:
"data": {
"Name": "Toy Panda",
"Description": "<ul><li>Zugriff auf über 6 Mio. Firmen & 22 Mio. Kontakte</li><li>Zugriff auf die Module Target, Connect, Datacare & Promote</li><li>3 Benutzerlizenzen und 15.000 Credits</li><li>Zugriff auf die Dealfront Academy</li><li>Professioneller Support per E-Mail, Chat & Telefon</li><li>Verfügbare Integrationen in Salesforce, Microsoft Dynamics 365, HubSpot CRM, Pipedrive, Zoho</li></ul>",
"Price": 10,
"QTY": 3
}
or
"data": {
"Name": "Toy Panda",
"Description": "• Zugriff auf über 6 Mio. Firmen & 22 Mio. Kontakte \n • Zugriff auf die Module Target, Connect, Datacare & Promote \n• 3 Benutzerlizenzen und 15.000 Credits \n • Zugriff auf die Dealfront Academy\n • Professioneller Support per E-Mail, Chat & Telefon\n • Verfügbare Integrationen in Salesforce, Microsoft Dynamics 365, HubSpot CRM, Pipedrive, Zoho",Comment actions
Please sign in to leave a comment.
Comments
9 comments