nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

S123 PDF Reports with No Checkboxes

CRossNSDA

I have noticed, just today, that all of my S123 reports that use the checked / checkbox option are not rendering at all when the PDF option is chosen. Example, ${EXT_GENCOND | checked:"ACCEPTABLE"}.

This just started happening today and all of my various reports are acting the same way so it is not on the report template side.

When I choose the DOCX option it works fine.

This is not a workaround that I want to deal with as I have many power automate flows that need to have the reports sent out as a PDF.

Vind meer berichten getagd met

Accepted answers

Ruth_JiatengXu

Hi @lklun ,

We have scheduled the deployment on June 22 at 8:00 PM PST. If no other issues are encountered, this PDF checkbox issue should be fixed after the deployment.

Thanks,

Ruth

All comments

Ruth_JiatengXu

Hi @EdenPettigrew ,

This might be an different issue, could you provide more details related to the docx dowload? e.g. error message shown in the job history

Thanks,

Ruth

Ruth_JiatengXu

Hi everyone,

The fix is now available on production site. Sorry for the inconvience, we will imporve the test coverage to prevent this kind of issue. We have also communciate within the team to ensure the critical issue can be fixed more quickly.

Thanks,

Ruth

EdenPettigrew

Following this too, my docx download isn't working either but that may be unrelated.

CRossNSDA

Our PDF reports were mostly generated via Power Automate flows so after hearing about this, I went in and changed our flows to generate a DOCX and then used a Convert to PDF flow connector and it will be my solution until the fix happens. I know this will not work for likely many folks but it was a fairly quick and easy interim solution for us.

pangue

Hi Ruth,

Please note that this behavior is not limited to the "checked" and "selected" expression methods. The Portable Document Format (.pdf) is not rendering characters (checked and uncheck box) even when manually entered in the template as text and could affect more characters than those referenced here. Please confirm that the fix includes these cases as well.

I am in a similar boat as the others, we use these reports for time urgent information. A 6-day report outage has critical impacts.

abureaux

@Ruth_JiatengXu

This is an unacceptable timeline... This feature not working is akin to the entire service being down. This needs to be fixed ASAP...

As has already been mentioned, we use this feature in our feature reports. With hundreds of reports per day across numerous feature reports, it isn't reasonable to regenerate reports or fix all affected feature reports. In addition to needing this patched sooner, can we please also get a response on why this slow of a timeline was chosen? 1-week is a very long time.

wunderlea

Also following, we're having this issue with critical reports including those for safety incidents.

RobBlash

Can't this be scheduled sooner? This is a big inconvenience. My company exports 100s of feature reports daily and they all include check boxes.

Ruth_JiatengXu

Hi @lklun ,

We have scheduled the deployment on June 22 at 8:00 PM PST. If no other issues are encountered, this PDF checkbox issue should be fixed after the deployment.

Thanks,

Ruth

SaadShahzad

We're also having this issue with a critical process. Would love if this is resolved ASAP!

lklun

Hi Ruth, do you have an ETA for the fix being pushed to production? I'd like to provide an update to my effected customers if able. Thank you!

BKonicke

Following. I noticed this issue Monday morning and manually generated time sensitive reports. After a couple hours of testing this morning and trying workarounds, I'm hopeful a seamless fix can be deployed by Esri soon.

abureaux

Activley following this as I also have this issue and need a fix ASAP.

Ruth_JiatengXu

Hi @CRossNSDA @RobBlash @TylerGraham2 @lklun

This issue was caused by a recent security update for the Report feature. After the dependency library was upgraded, its behavior changed, which caused this regression.

We have identified the root cause, fixed the issue, and verified the fix in our dev environment. We will deploy the fix to the production environment later.

I will let you know once the issue has been resolved in production.

Thanks,

Ruth

lklun

Submitted a case to Esri for this as well, we're thinking the PDF report engine isn't recognizing the symbol for the checkmark. If you embed fonts (i.e. use Times New Roman), you just get an empty square returned.

RobBlash

Already on it, thanks

TylerGraham2

Thanks for sharing that!

If you haven't yet, make sure you or one of your GIS admins report it to esri as a support ticket so they get official notification of the problem.

RobBlash

Confirming I'm seeing the same behavior so this is not an isolated issue. The docx -> pdf is the workaround for now, but not ideal since it involves additional work for my team.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.