Syteline 8 Dataviews – Multiple IDOs


Introduction

I ran into someone at the last Syteline User Group who asked the following ……..

“We use some data views for forms like Job Materials and Job Operations, however they may be of some use to our customer service department as well. We wondered if there was a way to bring information from say ‘Customer Order Lines’ or ‘Estimates’ into the data view for ‘Customer Orders’? “

This post is a very quick outline of how I would give the customer services team what they have requested. DataViews are a great tool with lots of possibilities – this is barely scratching the surface so if you want to know how to resolve a particular issue, please get in touch

Setting up the Data View

 

1) Open the Form “DataViews Setup”, and create a new record & give it a descriptive name

Infor Syteline DataView Setup New

2) For the first IDO – select “SLCustomers”, then save the record

3) Click the “IDO Setup” button, then do the following

I. Select the fields you wish to see from the IDO

II. Set the “Record Cap” accordingly – 200 rows on a form is often plenty, but a dataview often needs more – consider this carefully though as it could cause performance issues!

III. Set any IDO Filters you are interested in (For example I want to see everything summarised under a single customer, and we have thousands of ship to’s set up so I have set a filter of cust_seq = 0)

 

Infor_Syteline_DataView_IDO_Setup

Infor_Syteline_DataView_filter_Setup

4) Set up the Secondary IDO – This is where it gets a little more interesting. On the “DataViews Setup” form, enter the secondary IDO name, and the parent IDO name as shown here :-

 

Infor_Syteline_DataView_Setup_Secondary_IDO

5) Go back to the IDO Setup form and we now need to choose how we want the IDO to link. The first choice is “Multi-level” or “Single Level”. If it’s a one to one relationship, single level is probably best, a one to many, multi level is better in most cases, but not all. Then select the “link By” properties – not you can have as many or as few of these as you so wish. Finally, select the fields you are interested in seeing within your view.

Infor_Syteline_DataView_IDO_Setup_Secondary_IDO

 

 

6) Launch the DavaView from the “DataViews Setup” form and work with the layout until it is as desired. REMEMBER to save your layout and make it default, May times I have lost a layout I have been working on as it does not ask you when closing the form!

7) It is worth noting I was asked about “Estimates” and “Orders”, because an estimate is an order but with an “E” prefix, using a single secondary IDO collection has had the desired result HOWEVER, you may wish to see these grouped differently. To do this I would add a custom column, then group by that custom column as shown here :-

Infor_Syteline_DataView_Custom_Column

 

Infor_Syteline_DataView_Show_Group_By

 

Infor_Syteline_DataView_Finished

 

Making your Dataview Accessible

 

Most Infor staff will advise you that using the dataview icon on the top of any form is best – we have never found much of a use for these, and normally add buttons or links to forms so as the users can run the data view. Each of our departments has their own “Shortcuts” form and we have various useful links off of that for them, this saves any major upgrade issues.

 

To run a dataview, you must Run Form As Modal Child it will not work in any other way from my experience. But the parameters are straight forward as shown here :-

Infor_Syteline_DataView_Link

 

 Sharing DataViews

Finally – why re-invent the wheel! If you’ve written something useful, share it with others using the form “DataViews Import / Export”

 clicking this link will take you to a text file that you can rename to .xml and import PBTI_CustomersViewInfor_Syteline_DataView_Import_Export

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.