Answered by:
Sales Pipeline Report Issue

Question
-
Hi,
One of our users has reported an issue with the Sales Pipeline report in Dynamics CRM 4.0 (with Update Rollup 6 installed) - when viewing the report (grouped by date), they do not see any records when drilling-down into specific months (despite being able to see the chart and being able to view all opportunities when selecting the 'Show All' option underneath the chart). This issue does not affect all users, however those users who can drill-down successfully see '#Error' in the section headings (instead of the dates I'm presuming).
I've double-checked the roles that have been assigned to this particular user as well as team membership, etc. but can't understand why they can't drill-down whilst other similar users can.
Any assistance would be greatly appreciated.
Thanks!
Monday, September 7, 2009 10:52 AM
Answers
-
Could be a date issue, are you able to run the report successfully as the System Administrator? I'll assume that all users have their Time Zone options set correctly in CRM, this is the 'canned' Sales Pipeline report that is delivered with CRM and no changes were made to it.
I am able to run the report successfully on a few environments that I have tried in the U.S., but I have update rollup 5 not 6.
Best Regards, Donna- Proposed as answer by Donna EdwardsMVP Wednesday, September 16, 2009 11:43 AM
- Marked as answer by NJC1 Wednesday, September 16, 2009 12:29 PM
Tuesday, September 15, 2009 4:09 PM -
Thanks for your speedy response - it turns out that the users who were having problems had their workspace configured to use UK formats for dates whilst everyone else was using US formats - so basically the report works (although we're still seeing #Error headings) if you display dates as mm/dd/yyyy but not dd/mm/yyyy. Is this a known issue with a fix or workaround as this could lead to confusion as we're accustomed to using dd/mm/yyyy?
- Marked as answer by NJC1 Wednesday, September 16, 2009 12:29 PM
Wednesday, September 16, 2009 10:22 AM
All replies
-
Just to rule out security role issues, assign the user that is having a problem a 'default' Security Role, meaning one that is delivered with the CRM installation and has not been created, copied from a created role, changed, etc.
If the user still has the issue, have the user login from a machine that is working for another user and see if the user experiences the same result.
You can also check the Event Viewer for errors on the CRM Server and / or Report Server.
Best Regards, Donna- Proposed as answer by Donna EdwardsMVP Monday, September 14, 2009 7:29 PM
Wednesday, September 9, 2009 8:34 PM -
Thanks Donna, the user is already assigned one of the default roles but I will try your other suggestions and let you know how I get on.Tuesday, September 15, 2009 12:52 PM
-
I had the user log on to my PC and access CRM from there but unfortunately the result was the same. I've had a look through the event logs on both the CRM server and the SQL RS server but there's no indication of any issues.
Some other people on the forum have mentioned issues with dates as causing problems with this report - I'm wondering whether the issue I've reported is related to this, given that we're seeing '#Error' in the section headings for those users who can successfully access the report (and that we're working with dates in UK format dd/mm/yyyy)?Tuesday, September 15, 2009 3:25 PM -
Could be a date issue, are you able to run the report successfully as the System Administrator? I'll assume that all users have their Time Zone options set correctly in CRM, this is the 'canned' Sales Pipeline report that is delivered with CRM and no changes were made to it.
I am able to run the report successfully on a few environments that I have tried in the U.S., but I have update rollup 5 not 6.
Best Regards, Donna- Proposed as answer by Donna EdwardsMVP Wednesday, September 16, 2009 11:43 AM
- Marked as answer by NJC1 Wednesday, September 16, 2009 12:29 PM
Tuesday, September 15, 2009 4:09 PM -
Thanks for your speedy response - it turns out that the users who were having problems had their workspace configured to use UK formats for dates whilst everyone else was using US formats - so basically the report works (although we're still seeing #Error headings) if you display dates as mm/dd/yyyy but not dd/mm/yyyy. Is this a known issue with a fix or workaround as this could lead to confusion as we're accustomed to using dd/mm/yyyy?
- Marked as answer by NJC1 Wednesday, September 16, 2009 12:29 PM
Wednesday, September 16, 2009 10:22 AM -
Hi, you're welcome.
I don't know if there is a workaround, but it seems to me that things should work if the system is configured correctly. When you go to Settings, Administration, System Settings, and go to the Format tab, do you have English(United Kindom) selected? If so, it seems like users should be able to select the same option for their settings and run the report successfully.
If you have all the settings selected that I referenced and are still having this issue, then it will probably be a good idea to close this post as answered since the issue with the one user is resolved and open a post for this specific issue. Hopefully someone from the UK or someone who has a UK configured system will have the solution.
Best Regards, DonnaWednesday, September 16, 2009 11:43 AM -
Thanks Donna, I'll do that. In terms of the overall settings, yes we do have English (United Kingdom) selected at the server level. In the meantime I'll look back through the opportunities that have already been input and see if some of the dates have been entered incorrectly (hopefully the validation which takes place on input / save should have picked up any issues but if not it might explain why we're seeing errors in the report itself).Wednesday, September 16, 2009 12:29 PM