If you’ve ever used JavaScript to modify UI or enable a non-native workflow in a Quickbase app, this post is for you. We know that adding custom code to an application can be a valuable way to extend...
Updated 10 months ago
Version 2.0
Blog Post
@Evan Martinez, I think my #1 concern with this is the aggressive timeline for Rich Text. We have at least one very large "multi-use" Rich Text button field where various JS solutions/features are buried inside a large nested IF/Case statement. Each "THEN" is a different JS feature requiring its own independent migration effort.
A few questions:
1. We won't lose functionality in April, but will we lose the ability to incrementally remove individual JS features from this field described ? Example: remove 1 JS feature and Save (net reduction in total JS within the field)
2. Assuming a field only has 1 JS solution in it, can we edit it later to remove JS and still save on the same Field ID ?
3. Will we be able to change other properties on the field such as field name/label after a cutoff date ? Or is the entire field essentially shut down until we make a new one to replace it ?
A few questions:
1. We won't lose functionality in April, but will we lose the ability to incrementally remove individual JS features from this field described ? Example: remove 1 JS feature and Save (net reduction in total JS within the field)
2. Assuming a field only has 1 JS solution in it, can we edit it later to remove JS and still save on the same Field ID ?
3. Will we be able to change other properties on the field such as field name/label after a cutoff date ? Or is the entire field essentially shut down until we make a new one to replace it ?