Rich Text Field Change in April
Hello builders! Earlier this year we announced some upcoming changes to how Quickbase will handle unsupported code (like JavaScript) when it is placed outside of code pages. Read our recent blog post for more details on what is changing, why we need to make these changes, when changes will happen, and what you can do to prepare. The first of those changes will take place in April 2021.
As of 04/23/2021, users will no longer be able to insert unsupported content (like JavaScript) into scalar Rich Text fields. This change DOES NOT affect Formula-rich text fields. This means that users will not be able to save changes to Rich Text field values that contain unsupported content like JavaScript or create and save new records with JavaScript in a Rich Text field. Instead, users will receive an error message warning the user about the unsupported content that exists in the field, and changes won’t be saved. Users WILL be able to save changes to other fields in these records.
Check the Inserted JavaScript Usage app to see if we detected any app(s), table(s), and field(s) that contain JavaScript in your account. To see exceptions that will be impacted by the April release, look for Exceptions with the value “3. Found in field output, field mode: user entry” in the Reason field. For more information on what’s changing in the April release, check out our release notes page.
If you have questions or need help, you can reach out to our Care team by submitting a support case, or you can engage one of our Quickbase Solutions Provider (QSPs), who are ready to assist.
- The Quickbase Product Team
