Blog Post
@Evan Martinez Thank you for the answer; but as you already know, it's a non-answer. I do understand that it's the only answer you have, and I'm not pointing fingers at you, personally.
Can you please verify for me which of the cutoff dates applies to iframes on forms? Even my QSP doesn't understand which date applies to those.
My bottom line is simple, and it seems a lot of folks will be in the same boat, though they may not be wording it as strongly. If I cannot continue adding these elements specifically to forms, I have to abandon Quickbase. Period. This HAS to be allowed in another manner, BEFORE the cutoff date, so there is no downtime on existing functionality or on adding new iframes within forms. If there is any downtime on that ability, then I am no longer a QB customer. There is no other alternative for me, and I won't / can't even consider such. Adding the functionality to code pages accomplishes nothing for me at all. These iframe inserts have to remain ON FORMS.
I have also put in a request through the help system, and my QSP is looking for answers. Due to the fact that I have all documentation from time of sale, including a recording of a tech call/screen share where I was shown this functionality to secure the sale, if this function goes down, I will be looking for two years of full refund, as well as any cost for QSP development, from QB. I won't elaborate any further on a public forum, but I'll make as big a deal of this as a little company from Texas can make, and from reading all the community posts and commentary here, I don't think I'll be the only one. QB needs to really consider their customers here, and they need to consider what is the right move for their business in a world where public reviews and comments can make or break even a large company's business and public reputation.
I just need answers. And I don't need to have to wait until even closer to the deadline. If this functionality won't exist soon, I need to start app development on a competing platform YESTERDAY.
Even if iframes had to be submitted and approved, and the workflow was slowed... I don't understand the "security issue" and I don't care to. It's not an issue that affects me or my company's app, so it's not relevant to me. I don't need to understand the tech side of it. I need to know what the solution is, or will be. And I need to be ensured that the new method will be released before the old method is shut down.
Keep in mind that you're shutting down features your own team has designed for many of our apps. Saying it was technically never 'supported' isn't going to fly with your customers, nor will it fly in other venues due to precedent set by your own employees and QSP's.
Please do everything in your power to alert the powers that be to the fact that it's imperative they not close features without replacing them, breaking the apps many of us rely on to run our businesses. We placed a massive amount of faith in QB when we chose to hang the success of our businesses on your software, and your promises. This company is my only way to support my family, and over 100 other employees. This app IS the way we run our business. This isn't play time. These aren't video games. This is our livelihood y'all are screwing with, and yes... that one feature makes or breaks the entire product for my company's use. And I don't seem to be the only one. Y'all are the 'big guy' here. Treat your customers right. Do the right thing. Don't make this blow up. Please.
Can you please verify for me which of the cutoff dates applies to iframes on forms? Even my QSP doesn't understand which date applies to those.
My bottom line is simple, and it seems a lot of folks will be in the same boat, though they may not be wording it as strongly. If I cannot continue adding these elements specifically to forms, I have to abandon Quickbase. Period. This HAS to be allowed in another manner, BEFORE the cutoff date, so there is no downtime on existing functionality or on adding new iframes within forms. If there is any downtime on that ability, then I am no longer a QB customer. There is no other alternative for me, and I won't / can't even consider such. Adding the functionality to code pages accomplishes nothing for me at all. These iframe inserts have to remain ON FORMS.
I have also put in a request through the help system, and my QSP is looking for answers. Due to the fact that I have all documentation from time of sale, including a recording of a tech call/screen share where I was shown this functionality to secure the sale, if this function goes down, I will be looking for two years of full refund, as well as any cost for QSP development, from QB. I won't elaborate any further on a public forum, but I'll make as big a deal of this as a little company from Texas can make, and from reading all the community posts and commentary here, I don't think I'll be the only one. QB needs to really consider their customers here, and they need to consider what is the right move for their business in a world where public reviews and comments can make or break even a large company's business and public reputation.
I just need answers. And I don't need to have to wait until even closer to the deadline. If this functionality won't exist soon, I need to start app development on a competing platform YESTERDAY.
Even if iframes had to be submitted and approved, and the workflow was slowed... I don't understand the "security issue" and I don't care to. It's not an issue that affects me or my company's app, so it's not relevant to me. I don't need to understand the tech side of it. I need to know what the solution is, or will be. And I need to be ensured that the new method will be released before the old method is shut down.
Keep in mind that you're shutting down features your own team has designed for many of our apps. Saying it was technically never 'supported' isn't going to fly with your customers, nor will it fly in other venues due to precedent set by your own employees and QSP's.
Please do everything in your power to alert the powers that be to the fact that it's imperative they not close features without replacing them, breaking the apps many of us rely on to run our businesses. We placed a massive amount of faith in QB when we chose to hang the success of our businesses on your software, and your promises. This company is my only way to support my family, and over 100 other employees. This app IS the way we run our business. This isn't play time. These aren't video games. This is our livelihood y'all are screwing with, and yes... that one feature makes or breaks the entire product for my company's use. And I don't seem to be the only one. Y'all are the 'big guy' here. Treat your customers right. Do the right thing. Don't make this blow up. Please.