According to the Sage Developers’ blog:
Our recommended approach for deployment of new or customised Workspaces to a customer site is to create an Add-On (SDBX) package for it.
This approach makes deployment quite straight-foward. Eating our own dog-food has, however, shown that using the tool to create these packages is anything but straight-forward. To be honest, it’s quite painful and error prone.
[My emphasis added.] The author then goes on to explain all the ways Workspaces can be a pain but very helpfully offers a solution. Developers are like that. They do stuff because it’s useful and then they like to share it. Unfortunately, this solution hasn’t have past the Sage Taste Test (i.e. we can’t monetize it) because:
The caveats:
You will only be able to access this link if you are a registered Sage 200 Business Partner or Developer. Apologies if this causes you any inconvenience – if it does, please leave a comment and we’ll get in touch to find out what we can do. The tool will not be officially supported by Technical or Developer Support – again, please leave a comment with any questions, comments, suggestions or problems. The tool was created in my own time for my own convenience – and it’s been a long time since I was a professional developer… It has not had the level of engineering or Q/A rigour you would expect from an official Sage product (it isn’t one) and you should treat it with the same suspicion you would any other tool downloaded from the web!
This is a real pity. The author has obviously gone to a lot of trouble to try and be helpful though I am a bit tongue in cheek about his Sage quality statement. Given why he’s built the installer and the fact you have to be a registered Sage 200 partner etc the combined statements don’t quite hang together as a logical expression. What Sage should do is:
- Fix the issue or
- Put the installer through Q&A
In the meantime, it’s fair to say: Sage sucks – and it’s official. Unofficially? I leave that to savvy commenters.
Hat tip to Ed Molyneux




Comments on this entry are closed.
Get into the conversation