Deploying a grid after adding a new button in 9.6 impossible

Scriptcase 9 Bugs
#1

Deploying a grid after adding a new button in 9.6 impossible.
This issue hold me up to support my customers.
Killing…such bugs happens everytime there is a new release.
So I recommend not to upgrade before you have test everything in dept.
(Hmmm …Where you donot have the time for)
Problem is also you cannot go back in the release …SC does not offer this.

Of course I found after 2 days searching a solution:
Add the new button to an existing grid and copy the grid with a new name.
Example: copy the grid relations to relations1
Off course you have to repair the link…to the grid.

This all I give me the idea for a longer time already to stop with SC.
I will stay given support to existing customers. But I will offer to step over to a new system.
The whole proces will take a few years.
But there is no choice for me. I cannot allow me to my customers who have a production server to tell them that they have to wait a few weeks till SC is willing to repair.

The only way for SC in my opinion is to listen to there Customers and stop finding out features who nobody is waiting for. I cannot longer hold up with a fully responsibile solution.

#2

Hi,
there are at least 3 releases 9.4 / 9.5 / 9.6 that the changes are ridiculous. I’ve been saying for years that the SC team must listen to customers and not make unnecessary developments that destabilize the environment!
but no one has ever given my opinion on this forum!

#3

Yes I agree fully. Hope that SC is going to listen to their Customers…

#4

What system are you looking at ? SC is scaring me.

#5

Hi,
the question is not to change product but to make the SC team understand what are the things you need to improve the product! fix bug! just read the forum and there are dozens of bugs that SC can solve!!!

#6

@nwdbs: That is a good question, but the answer is not easy. SC is the best in price / functionality so far I know.
But during the 10 years I am working with it I only use a small part of that features. But the main thing is, that I hate the bugs which are case stoppers in production applications. I get red ears when a customer wants something done which should work and then I donot get it working in SC. I makes me unsure and thats what my customers feel also. There are some real alternatives but for me I think I going in the direction of a native PHP-platform (Laravel, PHSpeed and others) with tools to build a stable solution and which gives me the freedom and flexibility and 100% responsive (a must in 2020)
I donot believe in the RAD of SC versus this PHP-platforms. Ok you have to invest more time to study the language but after that you swimming in a warm sea. All depends of your needs and skills.

#7

@marcosc: to make the SC team understand is an impossible way to get out. I lost hope and with me others with a long and deep involvement in SC .Forget it. Sorry…

#8

@ctmservice I agree with your opinion. There are simply too many problems and bugs and the tool becomes more and more unreliable with each subsequent version.

Maybe the solution would be if the Scriptcase team listened to users and allowed us to install 2 versions with a single serial number.

For example, I’m still on version 9.04.032 and when I read all the problems of version 9.5 I didn’t even think about updating. Now with version 9.6 I also do not intend to make an update.
I have big projects for international companies (24 countries), (6 countries) etc. and exactly the same problems as you. I can’t explain to them why sometimes the simplest things don’t work after a couple of months.
However, if I could manage 2 versions with one serial number, it would be much easier. At 9.4 I would have working projects. At 9.6, new developments, project updates and stability testing.
Of course, Scriptcase will never agree to this. But even users in this case cannot agree to purchase 2 licenses as the blame for the unstable operation is not on our side.

1 Like
#9

@rik: How to change the SC team?

#10

@ctmservice: After 9 years of experience, I highly doubt I will see this.

#11

@ctmservice I agree with your opinion. I have a problem when I updated the version of 9.4.032 to 9.5.003 and I still have no solution. SC is not safe.

#12

hi,
I have been using it for 10 years but lately everything I can do with other environments I do.
SC Team must listen to their customers !!! I had been paying for gold support for 10 years but now I’m fed up I don’t get answers, I haven’t renewed it.

#13

Hello, @ctmservice

We really appreciate your feedback.

Please, have in mind that all suggestions given here will be considered.

About this issue you’re facing… can you tell me the steps to replicate it here in my environment (things like type of deploy and button)?

1 Like
#14

@roberttoferraz As you can read in the mean time it is not only the issue anymore, but more or less the trust in the development en support of SC. Before I put effort / energy in answering your question I suggest to organize a meeting (remote) with you and the management about the points mentioned.
I suggest that you invite the persons mentioned in this topic and perhaps other key users you know.
This in a small group. In that we can make appointments and from your site to hear your opinion and vision on the points mentioned. Have a nice evening and hear from you and your management, Regards Bert.

1 Like
#15

Hi,
I’m sorry but your request will never be accepted. SC have ignored customers for years!

#16

Hi Roberto

I think what we are all saying is that we need to protect ourselves and our customers from bugs which cause us to stop our development. Taking a backup before upgrading and then restoring if there is a problem is not a reasonable solution. It’s a good idea for disaster recovery but too dangerous for trying out a new version of SC.

Instead, we need a way to try the new version but to go back to the previous version if we get a problem. The easiest way could be 2 licence keys - one only for test and one for live production. The test licence key could have some restrictions on it to prevent misuse.

Thanks and regards

Jeff

#17

This was already discussed years and years ago. I always make a full binary backup before upgrading and then start testing. The problem is that when you return to the previous version, you never know when to upgrade. A lot of fixes are not reported, and you can never be sure when your issue is fixed.

#18

What if we all attended one of their live seminars and then demanded, en masse, that they address the bugs prior to any Updates/Upgrades.

#19

It won’t work because I think the webinar is outsourced, which they won’t listen to either.
They haven’t listened to us for years and years either.
Maybe it’s time for something else.
I have a license until August 2022. (last extended on Black Friday :frowning: )
However, I am already intensively looking for ways to transfer all projects to another tool.
This is not easy, however, because I have obligations to customers.
Not to mention all the time spent on it that no one will pay for.

#20

But I always says: “How longer the way forwards, how longer the way back”.
Mail me if you want discuss more…I am on my way back and see there is a horizon already.
info@ctm-service.nl