Blog Post
We do not currently plan to modify or remove unsupported content (like your iFrames) from existing fields and they should continue to work as designed after the cutoff. However, they are still subject to some risk. Our engineers will be going forward with our monthly release cadence and it is possible, and likely in some instances, for javascript and unsupported html to break with future changes. In the interest of helping you make an informed decision, we have plans on our roadmap to enhance forms, both in making them look and also function better, but as of right now, we don't have specific dates and deliverables mapped out around the iframe functionality if that is what you need to help you decide. We are working to continually identify gaps from customers and to see if and how we can address them. With regards to unsupported Javascript insertion, we already have some cases where we have encouraged builders to use native functionality or made them aware of future enhancements to native functions to help with that but we can't speak to every case's future today.
For any billing conversations you are going to want to work with your account team. I have reached out to them to let them know you have concerns and want to have a conversation. This change is going to result in negative impacts for some customers, but for most, security and control of their Quickbase ecosystem is paramount, and it is our responsibility to deliver that to them. As an organization we have to be critical and balance those two perspectives. That does mean at times we have to make and take ownership of decisions that not every customer will agree with. We will continue to evolve as the needs of our customers evolve. Your feedback is absolutely important and valid as we make these changes and we are here to hear it and help you make the decisions you need to make.