Hi, I would like to send a page break in the Quote Template to start a new page. The Terms and Conditions (fine print) needs to print on a separate page.
Platform is On Demand, Ultimate.
Hi, I would like to send a page break in the Quote Template to start a new page. The Terms and Conditions (fine print) needs to print on a separate page.
Platform is On Demand, Ultimate.
This should be standard functionality in 2023!
Hi Norm Bonenfant,
You can perform this by using Sugar's Doc Merge functionality. You can make the template and add any Word formatting, such as page break(s), without any additional coding. You can read more about Doc Merge at these links:
I hope this helps!
-Alex
Alex Nassi
Digital CX Operations Director
SugarCRM
Unfortunately, Doc Merge is nearly useless for us. We use comment lines to separate options for the customer, such as work being done in the "Kitchen" versus the "Dining Room". Since Doc Merge does not handle comments well and jumbles them into one bunch, misses some, etc. We can not use it. I know groups work but unfortunately that does not work with Faye's Quickbooks integration and would be many thousands of dollars for them to implement. One step forward, two steps back...
Hi Norm Bonenfant ,
It sounds like you're using Faye's Quickbooks integration correct? Do you have their latest package installed in your instance? Did you try to contact them going through your use case? They are very responsive and should be able to help.
Yes, we have the latest package and the enhancement for making groups work is around $3k or so. Not a terrible cost but I tend to struggle to justify paying to upgrade their system, when I feel like it is making it more functional for others. If that makes sense.
Yes, we have the latest package and the enhancement for making groups work is around $3k or so. Not a terrible cost but I tend to struggle to justify paying to upgrade their system, when I feel like it is making it more functional for others. If that makes sense.
Understood Norm Bonenfant thanks for sharing.
We, at the product level, are tracking and considering fixing/implementing this behavior.. You can find it in your portal by Issue & Ideas #92299...