Portal Errors first time loading

RE: Portal Errors first time loading

anshumanm — Wed, 04 Feb 2026 19:38:38 GMT

Thank you for the suggestions. I have tried implementing some pretty extensive null checks, and I tried using the expression rule to handle them cleanly, however it still results in the same error. I plan on opening a support ticket as Stefan suggested.

RE: Portal Errors first time loading

Mike Schmitt — Wed, 04 Feb 2026 19:30:40 GMT

For real.

RE: Portal Errors first time loading

Stefan Helzle — Wed, 04 Feb 2026 19:00:51 GMT

If something "does not load fast enough" making any depending code break, I would consider this a major platform issue, but not something I, as a developer, would have to take care of!

I suggest to open a support case to discuss this with Appian.

RE: Portal Errors first time loading

Mike Schmitt — Wed, 04 Feb 2026 18:38:10 GMT

Per what Shubham correctly noted... the text() function is finnicky when receiving null values. For this and many other uses, I have long since implemented my own custom rule, let's say "GLBL_SafeText()", which handles null-checking (removing the need to manually do this every single time you use the function in a place where a null value is even remotely possible).

if(
  a!isNullOrEmpty(ri!value),
  null(),
  
  if(
    a!isNullOrEmpty(ri!format),
    tostring(ri!value),
  
    text( ri!value, ri!format )
  )
)

RE: Portal Errors first time loading

Shubham Aware — Wed, 04 Feb 2026 16:41:59 GMT

The query isn’t returning data fast enough on initial portal load, causing the rich text field to reference null values.

Add null-handling checks before accessing nested data. The code already has a!isNotNullOrEmpty() check but needs to verify local!recentReports itself isn’t empty before accessing [1].