Sage MAS 90 and 200 Sage MAS 500 blogs Product Feedback Support Training
Reply
Sage MAS 500 Customer
rebekahg
Posts: 2
Registered: 10-27-2009
0

BI Dashboard Top Customers pulling wrong data

We are getting ready to start using BI Dashboard. Everything seems to be functioning properly, with the exception of the Top Customers web part. That widget is reporting data that appears to be from 2004.  We have verified that all financial periods are closed properly. All other widgets seem to be reporting current year/period data.

 

Has anyone else experienced this issue, and if so, how did you resolve?

 

Thanks in advance.

 

Sage MAS 500 Customer
DGill
Posts: 218
Registered: 11-06-2008
0

Re: BI Dashboard Top Customers pulling wrong data

I'm sure you are aware that there is a latency in the data that if you close the periods, you will not see the updated data until the following day?  The default schedule for the SQL job that fills the tables used by the dashboard runs 1x/day at night.  You could change this but would want to verify it does not performance issues running it during the day. 

 

Our Controller did identify an issue like what you described although I do not recall if it was Top Customers or Top Items.  Initially we were not current with closing off all the old periods which was an issue but even after doing that, he still identified the issue.  I have not been able to go back to figure out what the issue is, it has been a low priority as we see little use for this application.

 

 

Sage MAS 500 Customer
rebekahg
Posts: 2
Registered: 10-27-2009
0

Re: BI Dashboard Top Customers pulling wrong data

This is not an issue related to period close. All other widgets are pulling data as expected. This widget is pulling data from 5 years ago.  We have tried reopening and reclosing the periods, yet the issue remains.

 

At this point I am simply at a loss as to what to try next.

Sage MAS Partner
LouDavis
Posts: 545
Registered: 10-29-2008
0

Re: BI Dashboard Top Customers pulling wrong data

The widgets are usually tied to a stored procedure or a view.  I recommend running a detailed SQL trace to see what statement is being run that populates the Widget.  This may give you a clue of what needs to be changed.
Louis Davis MCSD, MCAD, MCITP
e2b teknologies, inc
www.e2btek.com