• Sage 300 Web UI SDK – Adding JavaScript

    Introduction

    Last week we talked about adding UI controls to our Web UI project. In the early days of the Web, this would be all you needed to do. The user would just enter the data and hit save (or submit). However modern Web applications are expected to be more responsive and interactive. This is achieved by adding JavaScript code which can perform local processing or make calls to the server for additional data or…

  • Sage 300 Web UI SDK – Adding UI Controls

    Introduction

    In my last posting I showed how to quickly create an empty Sage 300 Web UI by running our two new wizards from Visual Studio. In this article we’ll look at how to add some visual controls to this project and talk a bit about some of the issues with doing this, namely about using our provided HTML helper functions and CSS styling.

    We’re basically going to continue on and add the visual elements for the…

  • Introducing the SDK for the Sage 300 Web UIs

    Introduction

    Sage 300 has always provided an SDK to allow ISVs to create accounting applications in the same way that we create our own applications like General Ledger or Order Entry. In the past our internal application developers have usually only had the SDK installed for doing their own work.

    Further these ISVs can install their applications into a working Sage 300 installation by just copying a specific set of folders…

  • Sage 300 2016 Operations Beta

    Introduction

    We recently released Sage 300 2016 with Web UIs for C/S, Bank, Tax, G/L, A/R and A/P. Now we have released our first beta of the operations modules I/C, O/E and P/O. Internally we are calling this our February 2016 release, I’m not sure what it will be officially called externally yet. This release will be packaged as a Service Pack to the Sage 300 2016 version, so this will need to be installed first. This…

  • Sage 300 Web UI Internals

    Introduction

    At Sage Summit 2015 we introduced our new Web UIs for Sage 300. I’ve blogged a bit on the various user facing parts and a bit on the technologies used, but I haven’t had a chance yet to get into the internals of how they work. We’ve released the Web UIs for the Financial Modules and will be releasing the Operations Modules early in 2016. With these we will be releasing our SDK as well. Over…

  • Accounting in the Web with Sage 300

    Introduction

    We are just rolling out Sage 300 2016 which includes Web versions of Common Services, Bank Services, Tax Services, General Ledger, Accounts Receivables and Accounts Payables. The focus of this release isn’t on a new flashy portal with flashy KPIs (although we do have those) or other new technology enabled functionality. The focus is on the core Financial Accounting functionality; on entering financial…

  • Skills for Developing for Sage 300c

    Introduction

    With the Web UIs in Sage 300c rolling out in a couple of weeks, there is a lot of interest in the SDK and how to develop for this platform. We are still putting together the SDK, but in the meantime you can learn the technologies that are involved in developing our new Web UIs. Generally we’ve used off the shelf components both commercial and open source to develop our new UI framework. The good thing about…

  • Bengaluru Travel Blog Part 4

    Introduction

    As part of developing all the Web Screens for our upcoming Sage 300 2016 release, we worked with quite a few contractors at Sonata in Bengaluru, India. I originally visited them back in November 2014 and wrote a series of three blog articles on my experiences over there (part 1, part 2 and part 3). I then visited them again in March 2015, but didn’t blog about that visit. Now I’m in Bengaluru again and thought…

  • The Sage 300 2016 KPIs

    Introduction

    The new Sage 300 Home Page provides a nice launching point for running your new Web based Sage 300 Accounting screens. It also provides a Home view where you can choose to display up to six KPIs out of a palette of twelve.

    The twelve KPIs give a good selection of things from G/L, A/R and A/P since these are the accounting screens we are including with the first release. Then there will be more KPIs with…

  • Scaling and Availability for the new Sage 300 Web UIs

    Introduction

    I introduced our new Sage 300 Web UIs, talked about installing them and then discussed security implications. Now the question is that you have hundreds of users and things are starting to run quite slowly, what do you do? Similarly suppose you are all happily using the Web UIs and the web server hardware breaks down or Windows Update kicks in or Windows fails for some other reason? These two problems are…

  • Installing the New Sage 300 Web UIs Securely

    Introduction

    Sage 300 2016 comes with new Web UIs. With beta release I talked about how to install these, but I didn’t get into the details of securing your setup to be exposed to the Internet. If you just follow the instructions from the last blog post, then you are ok in a protected LAN environment, but need a number of additional steps to go beyond that. A common question is how I set this up in a secure manner so…

  • Installing the Sage 300c Web UIs

    Introduction

    In my last post I introduced the new Web UIs for Sage 300. This blog post is on installing the new Web UIs for Sage 300. The product has just gone to beta so I thought it might be helpful to provide a few details on the installation process. I also included details about some rough edges in the beta installation. I’ll update this article as we go along with any problems encountered and helpful workarounds…

  • Sage 300 Moves into the Browser

    Introduction

    Probably one of Sage’s worst kept secrets is that we’ve been working on a true Web version of Sage 300. Now finally at Sage Summit 2015 the cat is out of the bag and the product is officially announced as Sage 300c. You can see the announcement in this video.

    We will be including Web UIs for G/L, A/P, A/R, Bank, Tax, C/S and A/S screens in the upcoming Sage 300 2016 release which is slated for…

  • Me and My Drone

    Introduction

    This article doesn’t have anything to do with ERP software or programming practices. I received a drone for my birthday this year and this posting is about my drone. My drone is a DJI Phantom 2 Vision+. Basically it’s a flying camera that can take still photos or videos. Its easy to fly and can do some quite amazing things.

    Privacy

    A lot of people are against drones because of privacy concerns…

  • Remembering Leonard Nimoy

    Introduction

    The original Star Trek came out in 1966 when I was only six years old. It only ran for three seasons but had a great influence on so many people. Leonard Nimoy lived a long life and did many things; but, to many of us he is still and will always be Mr. Spock. I think I spent my entire childhood watching the original Star Trek, first the original series and then over and over again in repeats.

    I’m amazed…

  • Performance and the Sage 300 Views Part 2

    Introduction

    Last week we discussed avoiding table scans when using the Sage 300 ERP APIs. This week we are going to look at some other issues to do with updating data and with processing meta-data.

    Last week I showed a cheetah running as an example of performance and speed (the fastest land animal), but this week here she is resting and getting some attention.

    AOM/UI Info/ViewDoc

    First, just if you are wondering…

  • Performance and the Sage 300 Views Part 1

    Introduction

    The Sage 300 ERP Views (Business Logic) give you a great deal of power to perform Accounting operations through our various APIs. However as in any programming, performance must always be taken into account. The Sage 300 ERP Views have a lot of features to help you perform operations with good performance, but like anything if they are used incorrectly, performance can be miserable.

    This article is going…

  • Drilldown in Sage 300 ERP

    Introduction

    Much accounting detail is entered in one application and passed on to another for recording. Drilldown is the ability to reverse the audit trail and display, application by application, the document back to its original entry into the Sage 300 ERP system. For example, in Sage 300 General Ledger (G/L), you can drilldown from General Ledger Transaction History to the Journal Entry, from the Journal Entry to…

  • On Calculating Dashboards

    Introduction

    Most modern business applications have some sort of dashboard that displays a number of KPIs when you first sign-in. For instance here area a couple of KPIs from Sage 300 ERP:

    To be useful, these KPIs can involve quite sophisticated calculations to display relevant information. However users need to have their home page start extremely quickly so they can get on with their work. This article describes…

  • CSQRY from the .Net API

    Introduction

    Generally in these blog posts I talk about how to access the Sage 300 ERP data through our various APIs that go through our Business Logic Views. This is the only way to update the data in a supported manner, but often for reporting needs something more is hoped for. We store our data in standard databases which are accessible via various APIs like Entity Framework, ADO.Net or ODBC. The downside is that…

  • Dabble in Startups But Keep Your Blue Chip Job

    Introduction

    Over the last little while we’ve lost some people to startups and we’ve hired a number of people away from startups, so what factors are causing this movement? Desire for greater autonomy and more flexibility? Or is it today’s version of a Klondike gold rush where hordes set out on the treacherous journey but few strike it rich?

    I’ve spent most of my career with the Sage 300 product whether…

  • The Sage 300 SDLC

    Introduction

    A lot of my blog posts are to answer questions that I frequently receive. Then I have a ready answer of a blog posting link, or perhaps people read my blog and it saves me receiving an e-mail. This blog posting is along the same lines as I get asked quite frequently about our SDLC (Software Development Lifecycle). Usually this is in regards to someone trying to fill out a giant RFP full of questions that…

  • Problems with Branching by Feature

    Introduction

    Back in January I wrote a blog on Branching by Feature. In this article I want to talk about some problems with branching by feature as well as talk about some other approaches. We’ve been doing branching by feature since a bit before the...

  • Sage 300 ERP 2016 SQL Server Only

    Introduction

    If you were able to attend the Sage 300 ERP roadmap sessions at Sage Summit you would have heard that the next major release of Sage 300 ERP (named 2016 but released in 2015) will be dropping support for Pervasive.SQL and Oracle as database servers. This means the only supported database will be Microsoft SQL Server. Although we will support several versions of SQL Server long with the Azure SQL flavor.