Skip to main content
Nintex Community Menu Bar
Solved

Issue rendering Skuid Page component TypeError: Class constructor Xt cannot be invoked without 'new'


Forum|alt.badge.img+7

Defect/Issue Description: All Skuid pages in my Salesforce org are throwing an error whenever any user tries to view them and then will not render.
A description of the bug The error that shows is 'There was an error rendering a Skuid Page component for page SKUID PAGE NAME TypeError: Class constructor Xt cannot be invoked without ‘new’. When you click out of that error, you immediately see a second error that simply says “Class constructor Xt cannot be invoked without ‘new’”

Environment:

  • API Version: (v1 or v2) v2
  • Release: (Chicago, Boston, etc) Chicago
  • Release version: (Version Number) 14.3.1
  • Platform: (Managed cloud or Salesforce) Salesforce

**Brief Summary of the Defect/Issue:**All Skuid pages in my Salesforce org are throwing two consecutive errors whenever any user tries to view them and then will not render.

An easy-to-understand description of the bug (e.g., “When mass selecting items (not including clicking the ‘select all’ checkbox), other checkboxes on the rows selected appear to take on a checked value.”). Whenever viewing an embedded Skuid page within a Lightning page in my Salesforce org (multiple objects and lightning pages and Skuid pages), the page will throw two consecutive errors and then will not render.

Action Performed:
The action that resulted in the bug Viewing a Skuid Page component within a Lightning page in Salesforce

Expected Result:
How the page should have performed Loaded as it previously did (issue started last week)

Actual Result:
How the page actually performed Throws two consecutive errors, does not load Skuid component.

Additional Resources:
Please add any screenshots, videos, XML file(s) to help us reproduce the defect/ issue. See [how to create a good test page]

Best answer by CRMF_Woj

Hey @Anna_Wiersema - I ended up working with Skuid’s support team to resolve this issue. It turns out that another custom component on the same lightning page was causing the error - it was using some sort of standard Javascript call that conflicts with how Skuid works. After updating the other custom component’s code to avoid using this Method, the error was resolved.

View original
Translate
Did this topic help you find an answer to your question?

annajosephine
Nintex Employee
Forum|alt.badge.img+18

Hi @CRMF_Woj are you using any custom code or custom components on your Skuid pages? If so, please check and see if you are able to view a page that doesn’t contain these things.

It sounds like you’re just getting this error in Lightning. Are you able to open your Skuid pages in the Composer?

Translate

Forum|alt.badge.img+7
  • Novice
  • July 12, 2024

Hey @Anna_Wiersema - I ended up working with Skuid’s support team to resolve this issue. It turns out that another custom component on the same lightning page was causing the error - it was using some sort of standard Javascript call that conflicts with how Skuid works. After updating the other custom component’s code to avoid using this Method, the error was resolved.

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings