Hey Matt,

Just seeing this after the weekend. Hrm, I’m not positive what it could be. Do you see any clues in the JavaScript console, error-wise?

If not, here are the collection of Heads Up sections that seem relevant to custom code in the major versions since 10.0.27: 

- https://docs.skuid.com/v11.2.27/en/release-notes.html#heads-up
- https://docs.skuid.com/v11.1.1/en/release-notes.html#heads-up
- https://docs.skuid.com/v11.0.0/en/release-notes.html#heads-up

It seems the biggest things would be these two updates. Give these a read and see if they affect your code:
- https://docs.skuid.com/v11.1.1/en/release-notes.html#use-getrenderer-and-getfieldrenderer-instead-of-directly-accessing-properties
- https://docs.skuid.com/v11.1.1/en/release-notes.html#skuid-component-createchildcomponents-has-been-deprecated

And not sure if you’re trying this or not, but custom components are not currently supported in v2. I figure it’s just your v1 pages that are off, but I wanted to make sure to note that just in case.

Thanks. I’m investigating further. I attempted to update the to the skuid.ui.getFieldRenderers() function, but there is a conflict in the documentation. Some places use the plural, some the singular. Apparently getFieldRenderers() plural is not a function, but getFieldRenderer() singular is a function.

Ahhh yeah, this looks like a typo on our end. I’ll get that fixed now. Thanks for pointing that out!

You may have already updated it, but the same is true for skuid.ui.getRenderer() singular, not .getRenderers() plural.