Scripting

We're trying to import data into Sage 100 Premium (without using VI), and I was wondering if anyone had any thoughts to using SQL or BOI? As in are their any trials or road blocks we might run into? The task is that we are trying to import data from another SQL database into the SO_Invoiceheader and SO_invoiceDetail tables. One reason I've been trying the SQL instead I can't seem to find as much documentation/examples of how to use BOI to actually import data into Sage, but maybe I'm just looking in the wrong locations?

BOI is much slower, but it will enforce the business logic and integrity, so that would be my first choice. However, I don't think there's any bulk import, so you'd need to use BOI to create the individual entries and then update.

@SteveIwanowski by bulk imports do you mean the ability to import from say a excel file such as VI would? If so i may have found an example of that I could share.

Right. If it's bulk, VI is the way to go.

Great! Thanks for the information I'll keep plugging at this example I found but I would agree VI would be the better way to do this.

It may be semantics but we want to push data into the Sage SQL tables from outside of Sage, like BOI, using SQL tools as compared to ""importing"" data from within Sage, like VI. Source Data will not be dumped to an external file, or SQL staging table, to be prepared for an ""import"". We have lots of non-sage SQL integration resources available to us and would be a first choice if we can maintain data integrity. Anyone know of any good resources for learning use of BOI or interested in offering tutoring services for BOI?

Bad idea to push any data directly into Sage 100 via sql. So many things can go wrong with validation, referential integrity etc and if support catches wind of it, you'll be SOL.

thanks @MarkChinsky