Quickbase Development with Javascript Override & Custom Forms

The client runs an enterprise that utilizes Intuit Quickbase to perform several applications.

They have several pages with custom Javascript formulas in the formula fields and Quickbase just announced that they are no longer allowing Javascript in these formula fields.

These custom codes and how Quickbase is handling them outside of the code pages are going to likely disrupt our applications from properly functioning.

The client needs to have a developer be able to redirect all forms to a custom page instead of the current Quickbase forms.

Quickbase Development with Javascript Override & Custom Forms

‍Our Solution 

We helped the client to redirect all the forms to a custom page instead of existing Quickbase forms. We have quite an experience with JavaScript and its frameworks. We had done many projects with custom integrations using javaScript.

We reviewed the QB Apps. The issue with the JavaScript was there in the Insure Me Cloud App. We attached our findings for the client’s ease of understanding and estimated the required hours to complete those. 

Milestones achieved: 

MS 1 : - Insurance Reps Main Form - InsureMe View Form, insureMe20 View Customer - Edit Form, Client Main - InsureMe View Order - InsureMe Proposal 3.0, insureMe20 View, Proposal Administration

MS 2: - InsureMe jsButtons - Save Record - Formula Save Proposal - Formula Save Record - Save - Delete_Formula Save Record - Save - Save Record - Buttons

Quickbase created an app to identify where the client’s applications contain JavaScript in their account. To see exceptions that will be impacted by the August release, look for Exceptions with the value “1. Found in formula schema”, “3. Found in field output, field mode: formula”, or “4. Found in report formula” in the Reason field.

We completed most of the points in MS1 just some Points are pending below are the points we have completed

Insurance Reps Main Form - InsureMe View Form, InsureMe20 View Customer - Edit Form, Client Main - InsureMe

We implemented service worker technology as an alternative for IOL and have been successful in doing so, and also ensured that the custom code pages were being loaded and things were fixed. We tested the same for the buttons field in the customer table and it was working as expected. We also applied this to the rest of the Tables and forms

Quickbase Development with Javascript Override & Custom Forms

The client runs an enterprise that utilizes Intuit Quickbase to perform several applications.

They have several pages with custom Javascript formulas in the formula fields and Quickbase just announced that they are no longer allowing Javascript in these formula fields.

These custom codes and how Quickbase is handling them outside of the code pages are going to likely disrupt our applications from properly functioning.

The client needs to have a developer be able to redirect all forms to a custom page instead of the current Quickbase forms.

Quickbase Development with Javascript Override & Custom Forms

‍Our Solution 

We helped the client to redirect all the forms to a custom page instead of existing Quickbase forms. We have quite an experience with JavaScript and its frameworks. We had done many projects with custom integrations using javaScript.

We reviewed the QB Apps. The issue with the JavaScript was there in the Insure Me Cloud App. We attached our findings for the client’s ease of understanding and estimated the required hours to complete those. 

Milestones achieved: 

MS 1 : - Insurance Reps Main Form - InsureMe View Form, insureMe20 View Customer - Edit Form, Client Main - InsureMe View Order - InsureMe Proposal 3.0, insureMe20 View, Proposal Administration

MS 2: - InsureMe jsButtons - Save Record - Formula Save Proposal - Formula Save Record - Save - Delete_Formula Save Record - Save - Save Record - Buttons

Quickbase created an app to identify where the client’s applications contain JavaScript in their account. To see exceptions that will be impacted by the August release, look for Exceptions with the value “1. Found in formula schema”, “3. Found in field output, field mode: formula”, or “4. Found in report formula” in the Reason field.

We completed most of the points in MS1 just some Points are pending below are the points we have completed

Insurance Reps Main Form - InsureMe View Form, InsureMe20 View Customer - Edit Form, Client Main - InsureMe

We implemented service worker technology as an alternative for IOL and have been successful in doing so, and also ensured that the custom code pages were being loaded and things were fixed. We tested the same for the buttons field in the customer table and it was working as expected. We also applied this to the rest of the Tables and forms

Quickbase Development with Javascript Override & Custom Forms

The client runs an enterprise that utilizes Intuit Quickbase to perform several applications.

They have several pages with custom Javascript formulas in the formula fields and Quickbase just announced that they are no longer allowing Javascript in these formula fields.

These custom codes and how Quickbase is handling them outside of the code pages are going to likely disrupt our applications from properly functioning.

The client needs to have a developer be able to redirect all forms to a custom page instead of the current Quickbase forms.

Quickbase Development with Javascript Override & Custom Forms

‍Our Solution 

We helped the client to redirect all the forms to a custom page instead of existing Quickbase forms. We have quite an experience with JavaScript and its frameworks. We had done many projects with custom integrations using javaScript.

We reviewed the QB Apps. The issue with the JavaScript was there in the Insure Me Cloud App. We attached our findings for the client’s ease of understanding and estimated the required hours to complete those. 

Milestones achieved: 

MS 1 : - Insurance Reps Main Form - InsureMe View Form, insureMe20 View Customer - Edit Form, Client Main - InsureMe View Order - InsureMe Proposal 3.0, insureMe20 View, Proposal Administration

MS 2: - InsureMe jsButtons - Save Record - Formula Save Proposal - Formula Save Record - Save - Delete_Formula Save Record - Save - Save Record - Buttons

Quickbase created an app to identify where the client’s applications contain JavaScript in their account. To see exceptions that will be impacted by the August release, look for Exceptions with the value “1. Found in formula schema”, “3. Found in field output, field mode: formula”, or “4. Found in report formula” in the Reason field.

We completed most of the points in MS1 just some Points are pending below are the points we have completed

Insurance Reps Main Form - InsureMe View Form, InsureMe20 View Customer - Edit Form, Client Main - InsureMe

We implemented service worker technology as an alternative for IOL and have been successful in doing so, and also ensured that the custom code pages were being loaded and things were fixed. We tested the same for the buttons field in the customer table and it was working as expected. We also applied this to the rest of the Tables and forms

Author

Admin

Follow us on

Send us a message

Related Glossary

© 2024 Laitkor. All rights reserved.