As you may have seen with the decrease of frequency of posts, after few years making customers stronger, we are slowly moving away from the Legacy Lawson Business Intelligence (LBI), Infor BI for Lawson or Infor Lawson BI, however you want to call it – but we need your help.
We are still committed to share knowledge, empower users and have customers get a better value per dollar. If you are with Infor and reading this, we are interested in working on the latest Infor BI releases on an educational basis and spread the knowledge to the community.
If you are able to help, send us an email to firstname.lastname@example.org.
There are known issues when using dynamic parameters with and ODBC-based Reporting Services data source. They mostly resolve around dynamic parameters that prompt end-users for username/password when trying to change them on-the-fly. In this article, we will explain how to get around those.
→ Read More on «Reporting Services and Dynamic Parameters Prompt»
We are inaugurating a new blog category dedicated to Smart Reports with this post. Having spent considerable time working with customers on this product, we thought it was time to spread the knowledge, keep reading!
→ Read More on «Infor Lawson Smart Reports: What You Need to Know to Get Started»
In a previous article, we have seen how to link SQL Server’s Management Studio, provisioned via the installation of Infor’s LBI or BPW, and DB2 – via Microsoft’s OLEDB provider for DB2. This required the installation of a piece of software.
This article demonstrate how to create such link out of the box.
Read the rest of this article here.
In the data world, being able to work from a familiar platform sourcing data from a third-party system is gold. This is why most data warehousing tools operate from a chosen database system. In this article, we will focus on getting connected to a iSeries/AS400/DB2 environment, via a Linked Server on SQL Server, all this through the Microsoft OLEDB provider for DB2. This provider is widely reported as being faster for data transfer.
Read the rest of the article here.
We received a request recently to aggregate the content of M3 datasets (OSSSET) into a single result set. The challenge with this dataset is that , at query time, table names are not known in advance. Their names vary based on creation time and M3 company. This article explains how to retrieve this data and present it in a single view.
→ Read More on «Dynamically Retrieve Content of M3 Dataset Definition Files (OSSSET)»
There are two ways to distribute reports with Reporting Services. One is to email the generated reports to the right recipient. The other is to send the document to a printer. For some time we have heard customers requesting the ability to move generated reports to a custom path (be it a network location or not). After few hours spent on the issue, not only we found a solution, but we opened new possibilities.
→ Read More on «Copy Scheduled Reports Output to Folders»
Data warehouses are great. However they are hard to setup and not necessarily worthwhile especially if the end goal is to produce a single report. iSeries/DB2 has the ability to generate temporary tables (also called session tables) that are available during a user session.
→ Read More on «Using iSeries/DB2 Session Tables to Emulate a Poor Man’s Data Warehouse»
Smart Notifications, or the “proactive exception-based engine” is central to Infor Lawson Business Intelligence. Apart from the classic training and the user guides, there are little resources available online to get you started, we aim at fixing this with this guide.
→ Read More on «A Beginner’s Guide to Smart Notifications»
We previously wrote how one can leverage stored procedures with Crystal and Reporting services, and the conveniences offered by this method.
When working from the iSeries platform, there are differences to be found in the way code is written. To be able to do so under iSeries/DB2, you will need the following code:
CREATE PROCEDURE mydatabaae.mystoredprocedurename ( IN myfirstparameter char(2))
DYNAMIC RESULT SETS 1
READS SQL DATA
CALLED ON NULL INPUT
SET OPTION ALWBLK = *ALLREAD ,
ALWCPYDTA = *YES ,
COMMIT = *NONE ,
DECRESULT = (31, 31, 00) ,
DFTRDBCOL = *NONE ,
DLYPRP = *NO ,
DYNDFTCOL = *NO ,
DYNUSRPRF = *USER ,
SRTSEQ = *HEX
<INSERT SQL STATEMENT HERE WITH THE SEMI COLON RIGHT AFTER>;
The various properties passed with the stored procedure will have to be checked by an experienced DBA to ensure they suit your particular needs, but this is an excellent start.
This code would have to be run within the iSeries environment, preferably through the iNavigator SQL prompt.