Skip to main content
Nintex Community Menu Bar
Question

Field Editor Component Not Displaying All Fields

  • July 11, 2024
  • 4 replies
  • 10 views
  • Translate

Forum|alt.badge.img+5

We have a skuid page that uses a Field Editor component. There are two columns in the component. Each column contains about 18 fields to display. We are having an issue where some of the fields in the data model that have been added to the columns do not display in the Salesforce record. In Skuid Preview mode they display, and in the lightning record page editor they display. But in the actual Salesforce record they are not visible (not the field label or the field value) even though I have refreshed/reloaded the skuid page in the record multiple times. What am I missing?

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

4 replies

Forum|alt.badge.img+11

Hi @Joan_Jackson, can you offer the following details about your setup?

  • Which Skuid release version you are using?
  • Are you creating v1 or v2 Skuid pages? (Sounds like v1 since you are using a Field Editor as opposed to a Form.)
  • Do you have a Skuid Admin or Skuid Page Builder permission set?
  • Are you viewing the Salesforce record with the same profile/permission set that is being used to develop the Skuid page?
  • Is the object whose fields are being displayed a standard or custom Salesforce object?
  • Is there any Salesforce field-level security on the object whose fields you are trying to display?
Translate

Forum|alt.badge.img+5
  • Author
  • 25 replies
  • July 12, 2024

Thanks Ryan, I updated our skuid package then migrated the skuid page to v2. That seems to have solved the problem. I can see the fields now that were missing before. If any other issues come up I will let you know.

Translate

Forum|alt.badge.img+11

Great! Thanks for following up, @Joan_Jackson. Glad to hear that the Skuid update and migration to v2 resolved your issue!

Translate

Forum|alt.badge.img+10
  • Scholar
  • 224 replies
  • March 25, 2025

I’m experiencing this bug as well but I am not at a point right now where I can update SKUID and I definitely cannot migrate to V2 any time soon.

I think however I’ve figured out why this happens, but it still seems like a very bad SKUID bug.

I have some model conditions set up on the model I’m creating a row in. With those model conditions there, in theory it should try to create the row with values based on those conditions, but it does not, and somehow the row breaks in the creation process.

The model with conditions, something in these first 2 conditions causes creation of new rows to break, but if you remove those 2 conditions and instead specify them when creating the row, it will work properly:

Creating a row. With the bad conditions on the model, whether or not you specify the row values here, the row will break, but removing the bad conditions on the model, the row creates properly:

The row that got created (with the bad model conditions), notice that even though I specified it to have an Account and Payment Method, these didn’t get filled in:

What the field editor looks like bugged, it should show a bunch of fields in both columns, but only shows the labels for 2 of the fields and nothing else:

 

This one definitely wasted many hours of my time trying to figure out what was going on. From now on I’m going to have to be extremely mindful of conditions placed on models if I’m looking to create rows in those models.

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