FetchXML reports in MSCRM Online do not work for more than 250. It throws generic error message - fetchxml

While running the FetchXML reports from BIDS(Business Intelligence Development Studio), all of them work fine with all filters applied.
But, when the same report is deployed to MSCRM Online, they throw a generic error message(message: error occurred, contact administrator). These deployed reports work fine when only few values are selected for specific filters(in online deployment). But they fail when all values are selected in filter. For ex, Account Performance Dashboard report has this issue. When we select Account filter up to 250 with all Finplan groups selected, it is working fine whereas it fails for more than 300+ accounts.
Conceptually whatever executes successfully in BIDS should execute successfully when deployed also. But this is not happening. Can I simply go to Microsoft Connect and raise bug? Or is there any step which I am missing?
Also the same query works fine in Advanced find, but it throws error in report(having selection more than 250) which works fine in BIDS.

I found it myself!
CRM online has restrictions and limits. Refer the below links. We cannot design huge query reports for MSCRM Online 2011
http://social.technet.microsoft.com/wiki/contents/articles/12601.crm-2011-timeouts-and-limits.aspx
http://blogs.microsoft.co.il/blogs/rdt/archive/2012/08/31/microsoft-crm-2011-timeouts-and-limits.aspx
http://msdn.microsoft.com/en-us/library/gg334634.aspx
In this document you will find general information about limits which could be put on place on a CRM Environment, I hope you will find this useful:
http://www.microsoft.com/en-us/download/details.aspx?id=27139

Related

SSRS Deployed Report Not Executing WHERE clause

I have an SSRS report that works perfectly in Visual Studio 2017.
But when I deploy it, the deployed report comes back with all the data, ignoring the filters in the WHERE clause. I know it's this because when I remove the WHERE clause from my Visual Studio report, the data matches the deployed report.
This report pings off a shared data source; the dataset is not a shared.
Even a simple WHERE tbl.flag = 'Y' does not seem to do anything to the deployed report.
Why is SSRS not recognizing the entire SQL?
Not really an expert in SSRS, I just make them based off some YT tutorials and deploy them to the link that was given to me, so any advice or links for research are appreciated.
Check the server setting in the report project properties in Visual Studio.
If they look OK then delete the server copy of the report and redeploy.
If the report does not reappear then that proves that the report is either
a. not being deployed (you should see an error in the visual studio output window), or
b. it's being deployed to where you think it should be.
From the web portal you can search for a report by name and it will search all folders on the server so if it did deploy OK, you could find it that way.
I have discovered the issues was some inline comments I had in the SQL. I had some comments above the WHERE clause using dashes, --, explaining the filter. Once I removed it, the report executed correctly.
I was also able to change the comment style to the /* <my comment> */ and it executed correctly. It seems that other style of comments with dashes made the server think everything afterwards was a comment, and therefore not executed.

CRM 2016 Reports: Some dataset are blank when the report is ran with a specific user

I have a report on CRM 2016 which runs perfectly when it is launched with admin user. However, when we launch it with a normal user, all the datasets are displayed perfectly, except for 1 dataset (which was added lately to the report). To note that all the stored procedures used by the datasets (including this new one) have the same security roles on the SQL database. In addition, when I run the report from the visual studio, all the datasets are displayed as well. Can someone please help?
Solved. It was a security role issue on the business unit level

Crystal Reports & SQL Database

We have a windows 2003 server with crystal reports running on this, that ties to a sql db. Yesterday afternoon all reports that I was trying to run suddenly started freezing. I thought initially it was device specific and it was my pc and tried several other devices. Then one of my analysts noticed he couldn't run some standard Thursday reports which also froze .. etc.. Where does the error log for each of these reports write to so I can investigate the root cause?
Running slowly will not necessarily produce an error. The best thing for you to do in this situation is run the SQL used in your reports directly against SQL server from management studio, this way you have a whole host of performance monitoring options, you will also get a better feel of what the issue could be. Continue to troubleshoot different factors procedurally and you should find the issue.

Specified query not executable here - pentaho reporting

So I've designed a report in Pentaho Report Designer 3.9 and previewed it and ran it on my machine and everything works fine.
I have an input paramater that is a dropdown list and gets its values from a query called Vertical-List.
Now the drop down works on my machine. However, when I publish the report to the Online interface and try to access it, I get a message that says "The Specified query 'Vertical-List' is not executable here". I don't know what that means and what to do. It worked this morning and suddenly it stopped working.
Please help a brother out.
here is the query that generates the drop down
SELECT
`verticals`.`vertical_id`,
`verticals`.`vertical_name`
FROM
`verticals`
Double check your datasource and query, especially the parameters. If you have parameters, remember that a parameter is read in the Pentaho Report Designer as ${parameter_name}.
Also double check that you have defined the datasource in your BI Server.

Sharepoint 2010 External Content Type list

I'm taking my first crack at creating an External list in Sharepoint 2010. I've taken 3 training classes in Sharepoint 2010, and am now trying to transfer my knowledge to my own development environment. I've followed the steps for creating my External Content type in Micorosoft sharepoint designer. I am connecting the External Content Type to a table in an external SQL Server Database. I've created a list specifying this External Content type. I've also given all authenticated users permission. I've verified that BCS is running, and all looks good. I've also checked and double checked the steps I used in creating the external content type and list, by referring to the lab manual from my Sharepoint class.
When I try to navigate to display the list, I get this very informative error message:
Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator.
Correlation ID:b7c91266-bbbc-4703-8704-beccbbd92de0
I've tried opening this page in Sharepoint Designer but this doesn't seem to help me. Has anyone experienced this problem before? Any gotcha's that I should be looking for.
Whenever you see a correlation ID, then you should be able to get more information on the failure in the ULS output. Search for that Correlation ID in the logs and you should get plenty of additional information.
If you don't find much in the ULS logs, then change the settings to log additional information.
you need to check selection of primary key of sql tables while retrieving data to list.
To capture the error being thrown, use the SharePoint LogViewer app from CodePlex: http://sharepointlogviewer.codeplex.com/
You need to run it on your server and hit the Play Button at the
top. This starts the Live Monitoring.
Refresh your page that will give you the error with the Correlation ID.
Stop The LogViewer and filter the results by the Correlation Field.
Copy and paste the ID from your browser into the filter field.
You will now see a list of what errors are being thrown in relation to the Correlation ID.
I hope this helps out!