Personalization, Customization and Productivity Tools

[kmandevi]

For all of the people that have been using MAS for the past couple of versions what is the probability that the scripts that are written for a current version will not work properly for future versions?

I understand this may be a difficult question to answer without knowing what changes will come in future versions of MAS 200.

Thanks in advance. 

Ken

[rmikolainis]

---

kmandevi wrote:

For all of the people that have been using MAS for the past couple of versions what is the probability that the scripts that are written for a current version will not work properly for future versions?

I understand this may be a difficult question to answer without knowing what changes will come in future versions of MAS 200.

Thanks in advance. 

Ken

---

This is why you do testing before doing an upgrade.

[kmandevi]

So obviously there is always a chance that a script will not work properly with a newer version.

I understand that tetsing will always be necessary.

Have you found that may of your scripts work after an upgrade?

If there were problems were they difficult ones to fix?

Thanks.

[connex · Accepted solution]

I have written 100's of scripts and most after the BOI interface was introduced with version 4.1.  I've yet to have one yet that didn't survive and upgrade.  Unless of course it was written for a legacy module that went to the BO platform.

I suppose that it would be possible to write a script in a way that was to work around an existing MAS programming issue that would break once the issue was fixed, but the author would by definition be aware of the likelyhood.

Also, as long as you stay with using published field and variable names you should do well. It is possible to reference unpublished variables available to the script (like '_TMPxxx$' ) that could be eliminated in future releases, but Sage has always taken care to preserve published field names.

[rmikolainis]

---

kmandevi wrote:

So obviously there is always a chance that a script will not work properly with a newer version.

I understand that tetsing will always be necessary.

Have you found that may of your scripts work after an upgrade?

If there were problems were they difficult ones to fix?

Thanks.

---

I've never had an issue with a script not working after an upgrade, BUT............ thats not to say that a script will never break or error from an upgrade. Hence why I said test it out first.

Better to find out its broke in a test company than for stuff to happen in a live environment.