Details about this thread
  • State Verified Answer
  • Replies 6 replies
  • Subscribers 317 subscribers
  • Views 2693 views
  • Users 0 members are here

Blank rows in Doc Merge PDF template

Christopher Hart
We have a template that used this logic successfully within wDocs. Nevertheless, during the transition to Doc merge, it now fills in all the product lines on the quote. I've wrote a new simple code that only populates the products if they meet specific criteria; however, I'm encountering persistent blank rows that have proven quite challenging to eliminate.
Any suggestions on how to eliminate the blank rows would be greatly appreciated!
Thanks in advance
Christopher

Fullscreen
1
{#products filter='Accessories'}{product_template_name.name capitalize='true'} {category_name} {/products}
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Fig 1: WDocs code

Fullscreen
1
2
3
4
5
{#products sort='cattest_c:desc'}
{if cattest_c=='Accessories'} {product_template_name.name}
{elseif cattest_c!='Accessories'}
{endif}
{/products}
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Fig 2:Doc merge new code

Fig 3: Doc merge PDF

Parents
  • 0

     CRM GURU  do you have any suggestion

  • 0 in reply to Christopher Hart

    Hi  ,

    I don't think your elseif statement is necessary since you only want products with a cattest_c value of 'Accessories'. The sort should also be unnecessary since you are only populating records with a single cattest_c value. Have you tried the following code? 

    Fullscreen
    1
    2
    3
    4
    {#products}
    {if cattest_c=='Accessories'} {product_template_name.name}
    {endif}
    {/products}
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Chris

    Co-Founder | SugarCRM's 2024 Global Outfitters Partner of the Year

  • 0 in reply to Chris Raffle

    Thank you, Chris. Unfortunately, your solution didn't resolve the problem. I've escalated the issue with Sugar and will share the solution here once available.

  • +1 in reply to Christopher Hart

    Hi  I raised a support case with Sugar and received the feedback below. I added a 3-column page layout between page breaks to the doc merge document template which resolved my issue. 

    "Our developers reviewed this issue and was not able to find a workaround. I suspect the current functionality causes table rows sharing the same relationship collections (related loops) to link to the same sub-rows (lines) in a table row (similar to how line items render on a Quote).

    I went ahead and filed 2 Issues: one outlining the blank rows and another I found when trying to work around the issue:

    https://portal.sugarondemand.com/#supp_Bugs/93326
    https://portal.sugarondemand.com/#supp_Bugs/93325

    One key detail I found was that this issue seemed to be limited to tables sharing the same row. When using collections outside of a table, the blank rows did not render.

    I'm afraid I was not able to find any workarounds to this issue except by not using a table. Perhaps you may be able to find a solution by using a 3 column page layout instead?"

Reply
  • +1 in reply to Christopher Hart

    Hi  I raised a support case with Sugar and received the feedback below. I added a 3-column page layout between page breaks to the doc merge document template which resolved my issue. 

    "Our developers reviewed this issue and was not able to find a workaround. I suspect the current functionality causes table rows sharing the same relationship collections (related loops) to link to the same sub-rows (lines) in a table row (similar to how line items render on a Quote).

    I went ahead and filed 2 Issues: one outlining the blank rows and another I found when trying to work around the issue:

    https://portal.sugarondemand.com/#supp_Bugs/93326
    https://portal.sugarondemand.com/#supp_Bugs/93325

    One key detail I found was that this issue seemed to be limited to tables sharing the same row. When using collections outside of a table, the blank rows did not render.

    I'm afraid I was not able to find any workarounds to this issue except by not using a table. Perhaps you may be able to find a solution by using a 3 column page layout instead?"

Children
No Data