Html template stopped working properly after AppSheet update. 4 apps affected. I need a help urgent!

Hi! Since yesterday, my HTML template now ignores the expression <p>&lt;&lt;If:ISNOTBLANK([1])&gt;&gt;</p> PAGE CONTENT <p>&lt;&lt;EndIf&gt;&gt;</p> p>. When column [1] is empty, the page must not be printed in the PDF. It worked for months until last night. It occurred in other applications that use html as a template. I believe there was a system update. I need support urgently because my work is being affected.

<p>&lt;&lt;If:ISNOTBLANK([1])&gt;&gt;</p>
<table style="width:90%" align="center">
<tr>
<td rowspan="3" style="width:3%"><img src="&lt;&lt;[LOGO2]&gt;&gt;" class="logo"></td>
<td align="left" style="width:3%">Empresa:</td>
<td align="left">Periseg</td>
<td align="left" style="width:3%">Regulador:</td>
<td align="left">&lt;&lt;[Perito]&gt;&gt;</td>
</tr>
<tr>
<td align="left" style="width:3%">Email:</td>
<td align="left">(PII Removed by Staff)</td>
<td align="left" style="width:3%">Fone:</td>
<td align="left">(51) 980259832</td>
</tr>
<tr>
<td align="left" style="width:3%">Segurado:</td>
<td align="left">&lt;&lt;[Nome do segurado]&gt;&gt;</td>
<td align="left" style="width:3%">Sinistro:</td>
<td align="left">&lt;&lt;[Número do sinistro]&gt;&gt;</td>
</tr>
</table>
<hr>
<h3 align="center">Item 1</h3>
<table style="width:100%">
<tr>
<td align="center"><img src="&lt;&lt;[10001]&gt;&gt;" class="image"></td>
</tr>
<tr>
<td align="left">&emsp;&emsp;&emsp;&emsp;&lt;&lt;[1001]&gt;&gt;&nbsp;&lt;&lt;[100001]&gt;&gt;&nbsp;&lt;&lt;[1000001]&gt;&gt;</td>
</tr>
<tr>
<td align="center"><img src="&lt;&lt;[10002]&gt;&gt;" class="image"></td>
</tr>
<tr>
<td align="left">&emsp;&emsp;&emsp;&emsp;&lt;&lt;[1002]&gt;&gt;&nbsp;&lt;&lt;[100002]&gt;&gt;&nbsp;&lt;&lt;[1000002]&gt;&gt;</td>
</tr>
</table>
<hr>
<footer>
<p align="center">Emitido em &lt;&lt;_TODAY&gt;&gt;</p>
</footer>
<p>&lt;&lt;EndIf&gt;&gt;</p>
<DIV></DIV>
<!--LIMITE DE PÁGINA-->

Solved Solved
0 32 1,731
2 ACCEPTED SOLUTIONS

Steve
Platinum 4
Platinum 4

@neemias wrote:

Any idea what caused this change and non-recognition of expression?


Developers make and release changes to AppSheet just about every day. It's not always clear to the developers what the side-effects of their changes will be, so it isn't always clear when those changes should be announced or noted in the daily release notes. The reality of this "continuing release" process is that we--the users--frequently discover bugs and have to notify the developers. The best way to do so is by contacting Support.

View solution in original post

Are you still seeing the same issue? There was a release in the converter which could have caused this behavior change and that release is now rolled back.

View solution in original post

32 REPLIES 32

Steve
Platinum 4
Platinum 4

Please contact AppSheet Support for help with this.

Thanks @Steve!

@Steve @Suvrutt_Gurjar Any idea what caused this change and non-recognition of expression? It was working normally for months and I haven't made any changes recently.

I too am facing an issue with a word document template with respect to alignment.

Did the PDF engine change?

 

Hi @Kunal_Jain, i believe so! The support team is working to fix the problem...

Steve
Platinum 4
Platinum 4

@neemias wrote:

Any idea what caused this change and non-recognition of expression?


Developers make and release changes to AppSheet just about every day. It's not always clear to the developers what the side-effects of their changes will be, so it isn't always clear when those changes should be announced or noted in the daily release notes. The reality of this "continuing release" process is that we--the users--frequently discover bugs and have to notify the developers. The best way to do so is by contacting Support.

Thanks Steve! Support is there to resolve the issue.

Hi Steve!

 
I just realized that the same error happened again. Last time you took 1 month to settle the situation, which brought a series of inconveniences and losses to the company where I work. Again, an upgrade in the pdf generator engine results in the disregard of conditionals established within the .html template.  Can you help me?

Hi, we updated the version of chromium used to generate PDFs (see release notes) yesterday, but the variable replacement (in this case removing the conditional "page") happens before it gets rendered. I tried to reproduce the issue you described but couldn't. I am still able to use this to conditionally exclude some content in an HTML template.

 

<!DOCTYPE html>
<html>
    <head>
        <title>pdf-template</title>
    </head>
    <body>
        <p>&lt;&lt;If: ([MyYesNoColumn])&gt;&gt;</p>
        <table style="width:90%" align="center">
        <tr>
            <td>My conditional content</td>
        </tr>
        </table>
        <p>&lt;&lt;EndIf&gt;&gt;</p>
        <p>This paragraph should always be here</p>
    </body>
</html>

 

Can you contact support who can gather some more information about your specific case.

 

Hi Fabian, can you provide the before and after to support so we can take a look and see if it looks like another bug in Chromiums LayoutNG that we could pass along, or if it's working as intended with that bug fix. 

If you happen to have a copy of the PDF from when this broke earlier in the year that'd be even better so we could compare without LayoutNG, with LayoutNG before the bug fix, and LayoutNG with the bug fix.

Thank you very much @Greg_Denton. I just sent the files to support.

could you please share the case id through DM to me? I can escalate the ticket to Greg!

Thanks @Greg_Denton. I reported it to support last Tuesday... hoping for a resolution.

Hi @Greg_Denton

any news? There are blank pages in all my pdf's... 

Same here. Pagination changed somewhere between 15th and 19th December. I use Google Doc to create PDF.

The reason seems to be an update in the PDF generator from Skia/PDF m107 to Skia/PDF m108.

See also the comments in this post: https://www.googlecloudcommunity.com/gc/Release-Notes/December-19-2022/bc-p/501404#M1351

Thanks!

Thanks for these details!

FYI.. our engineers are investigating/debugging the reason.

Are you still seeing the same issue? There was a release in the converter which could have caused this behavior change and that release is now rolled back.

Thanks Aleksi for the information. I confirm the roll back is successful.

Solved. Thank you.

@Aleksi Apparently the problem was solved and the expression returned to work, printing the report normally. I'll be watching for a few days and if there are any problems, I'll let you know here.

Okay good!

This issue seems to have resurfaced. The text alignment in columns in the generated PDF is not as per the template. Maybe there was an update in the PDF engine version?

Things were working fine for me 3 days back. 

@Kunal_Jain, yes, it happened again on 03/16/2023 and so far the problem has not been resolved. Surely there was a new update. This has caused me a huge inconvenience and from what I understand the support has not given due importance to this issue. I have professional applications that I use all the time and it hurts my business, as it hurts all users of the tool.

@Steve@Aleksi Is there anything you can do to speed up the problem?

Same here. The reason seems to be an update in the PDF generator from Skia/PDF m110 to Skia/PDF m111.

CC @Arthur_Rallu 

I just realized that the same error happened again. Last time you took 1 month to settle the situation, which brought a series of inconveniences and losses to the company where I work. Again, an upgrade in the pdf generator engine results in the disregard of conditionals established within the .html template.

Thanks @Fabian_Weller... monitoring the situation.

Top Labels in this Space