302 Found

Found

The document has moved here.

Knowledge Base

Our Knowledge Base covers a wide variety of technical topics, from the basic to the complex.

Some of my entries appear in red text. What happened?

The field containing red values is a multiple-choice field. The red values are "orphaned" values. An orphaned value is an choice that was removed from the list, but still appears in some records. By showing that entry in red, QuickBase is alerting you to this disconnect. If you add that entry back to the multiple-choice list, those values will appear in black again. To do so, you must edit the field's properties. (Learn how: https://www.quickbase.com/help/changing_field_properties.html)

If ALL your entries are red, perhaps someone changed the format of your text field from "type-in" to "multiple-choice" by mistake. You can change it back to "type-in" without losing any data. Again, to fix this, edit the field's properties (please see link in preceding paragraph).

If USER values appear in red, please read: https://www.quickbase.com/help/about_local_users.html to learn how to correct the problem.

Comments

re: One value in red - not an orphan

Hello,

 

My name is Brian from QuickBase Support. If you could visit support.quickbase.com , I'll be happy to take a look at this. Creating a case for this helps us to track our work, but more importantly it allows us to share private information about your app privately.

 

If you can request in the case that it be forwarded to me, that would be great!

 

Thanks,

Brian

QuickBase Support

One value in red - not an orphan

When we uploaded from a spreadsheet, only one field was in red. This value is in a multi-choice table we use many times daily - not an orphan.

Post new comment

The content of this field is kept private and will not be shown publicly.
Type the characters you see in this picture. (verify using audio)
Type the characters you see in the picture above; if you can't read them, submit the form and a new image will be generated. Not case sensitive.
302 Found

Found

The document has moved here.