Custom Object Table Not Rendering Causes Velocity to Fail? | Community
Skip to main content
N
nhabischWings
New Participant
September 5, 2023
Solved

Custom Object Table Not Rendering Causes Velocity to Fail?

  • September 5, 2023
  • 1 reply
  • 2315 views

Hello all!
Have a ticket in with Support but curious on any thoughts on this strange situation. We've got an email that pulls in custom object record data for a certain type of account and had an instance where someone met the criteria (Smart List-wise and Velocity-wise) to receive the email BUT the script output table did not appear.

Here's where it gets weird - initially when I pulled up the object in the database in Edge and Chrome, the object loads but after the first 3 entries it looks like this:
MicrosoftTeams-image.png
The page then stalls and eventually crashes without loading. This Lead should have about 13-15 records so it's obviously not loading them in.

My initial Support response was that it was possible a cache/cookie issue and when I open that Lead in an incognito window it loads as it should.

What I'm confused by is when I do a specific "Preview by List" and replicate the list and Velocity parameters - why does my Velocity script seem to fail when previewing in standard Edge or Chrome but then it works fine and displays the table within the email in an incognito window?

Guess I'm confused why what seems to be a UI bug would cause the actual table load to fail in the email?

Note: It's (as far as I am aware) not a Velocity issue as the script works perfectly with other test cases.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

Impossible to say without seeing the stored values. You could have an HTML element in a CO field, especially a <script>, which causes the browser to hang.

Also, it's better to avoid the word "table" when referring to COs. Even if they happen to be implemented in an RDBMS, for your purposes they're a collection of objects.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
September 5, 2023

Impossible to say without seeing the stored values. You could have an HTML element in a CO field, especially a <script>, which causes the browser to hang.

Also, it's better to avoid the word "table" when referring to COs. Even if they happen to be implemented in an RDBMS, for your purposes they're a collection of objects.

N
nhabischWingsAuthor
New Participant
September 6, 2023

Got it, I figured as such that it wouldn't be able to be diagnosed but was curious if anyone had encountered similar issues. I will go back to our data team to double-check if there's any issues there. 

Terms & ConditionsAccessibility statement

Loading footer...