Fig 1: WDocs code
Fig 2:Doc merge new code
Fig 3: Doc merge PDF
{#products filter='Accessories'}{product_template_name.name capitalize='true'} {category_name} {/products}
Fig 1: WDocs code
{#products sort='cattest_c:desc'} {if cattest_c=='Accessories'} {product_template_name.name} {elseif cattest_c!='Accessories'} {endif} {/products}
Fig 2:Doc merge new code
Fig 3: Doc merge PDF
Hi, AFAIK the same filter options should work with both Wdocs and Doc Merge, so maybe something went wrong durin the upgrade.
Have you tried Sugar support team?
Hi Christopher Hart ,
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?
{#products} {if cattest_c=='Accessories'} {product_template_name.name} {endif} {/products}
Chris
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.
Hi Chris Raffle 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?"
Sugar raised 2 bugs for this issue
https://portal.sugarondemand.com/#supp_Bugs/93326
https://portal.sugarondemand.com/#supp_Bugs/93325