I have a report where all fields are clickable and all columns are potential parameters. When a field is clicked, the report reloads (as a sub-report if it were) with the added parameter.
for example, i have a list of items, their descriptions, sizes, color, etc. When I click "Gold" for color it will reload the report with the color parameter set to "Gold"
This report used to work fine in CRM 4. It all works fine in Visual studio and report manager but when I upload it to CRM 2011; it no longer works. The report runs smoothly when initially run but clicking a field in CRM does nothing, it doesn't even give me an error. the page flashes but the same data is visible.
I have another report with an actual sub-report that works fine. Is it the recursion that CRM hates? I can't set the parent report to itself, I'm assuming that is the problem. is there a way around this since it works in other Microsoft products?
Alternatively, could I use reportviewer.serverreport.setparameters to set the parameters of the report? Never used this before so I'm not sure if this works for CRM.
Related
I'm using Dynamics Crm 2016 and I need to disable the next/previous record buttons in the form ribbon for particular pages. I've tried using jquery to hide the button, it's just an anchor, but that's not working. See below
$("[title='Next Record (Ctrl+>)']").hide()
I have that code on a web resource loaded on the form, set to run on the forn load event but it's not working. It works when run it in the web developer console (IE 11). Can I do this another way, using the Xrm toolkit perhaps?
I don't believe there is a supported way to do this. JQuery would be one approach, but it would be unsupported and potentially break with any updates pushed by Microsoft.
I have a ReportViewer (for SSRS) in an ASP.NET application.
The user enters in parameter information through the web form and then submits it.
The ReportViewer then returns a small report that shows counts of the information requested.
Next to these counts are links (assigned in BIDS) to link to the corresponding report using the parameters already entered.
It all renders fine until I click one of the links in the ReportViewer. It will then give the brief "Loading" dialog and then the ReportViewer disappears.
Not sure how to handle this and I can't find much information on it. I would ideally like the selected report to open in a new window (no URL bar, etc).
Please help!
This ended up being an issue with how ReportViewer was installed on our development and production servers. So when it seems like nothing else can explain what is going on with the ReportViewer... make sure the DLLs are properly installed on your server.
I have an SSRS report that employs RowGroups to group data. One of the fields used in the group is a field that stores a URL as text. I've set a Go To URL action on a textbox which enables it to act as a hyperlink that opens up the URL stored as text in a field (i.e. =Fields!URL.value).
The textbox works fine in BIDS and in Report Manager, but when the report is accessed through our custom .asp Reporting Application, the textbox loses this link functionality. It just becomes text. When the mouse is hovered over the textbox, the cursor does not change. I've created another textbox on the report outside the RowGrouping and configured it the same way, and it works fine in the Report Manager and on the Report Application.
Is there any particular configuration that could be restricting a Go to Action property when in a RowGroup on a Reporting Application? Could this be an issue with the report, or an issue on the Reporting App end?
If you are using the ReportExecutionService check to make sure Javascript is true in the device info parameter?
<DeviceInfo>
<JavaScript>True</JavaScript>
</DeviceInfo>
But you said it worked if it was in another part of the report?
link to <DeviceInfo> Details
Never really found an answer to this problem, but a work around I used was placing a textbox to the right of the grouped textbox, where the link seems to work fine.
I am in the process of migrating an existing web application from .Net 1.1 to .Net 4.0
The application originally used Crystal Reports 11 and in the process of migration we are upgrading these reports to use Crystal Reports 13 (CRVS 2010) SP3.
For one of the reports, the requirement is to show the entire data in a single page (the report viewer control is turned off). I am just not able to get it to work in the migrated report.
Thr properties set are:
DisplayToolbar : false (crystal report viewer control)
SeparatePages : false (crystal report viewer control)
Keep Together on all sections : true (in the rpt file)
Suppress Blank Section :true
As I did not have much in page footer I set the Reserve Minimum Page footer property. I also set Clamp Page footer property
However when my report is displayed in the page, I observe blank lines in between the content like in the sample below.
These gaps appear right at the point where I would have had the page break if I had enabled paging. This makes my report look odd on the web page. With the old application which used previous version of CR this was not the case. Is there a way I can fix this without having to revert to paging?
Apparently it is a defect in the current implementation. We have instead decided to revert to 12.x where this issue is not present. It is mentioned that this issue has been fixed in the new SP but we didnt try it out.
Refer SAP support forum:
http://scn.sap.com/thread/3284720
I have a strange problem that I see when switching to the ASP.NET designer in VS2010. It doesn't happen every time but once it's happened once it continues every time until I reboot.
Basically, when I click the "Design" button/tab to switch from the HTML to the designer, the text "Requesting Data..." appears in the status bar and the mouse pointer changes to and arrow with a spinning wait indicator. When this happens, the mouse continues to work but the keyboard input starts to fail. I can usually type but can't backspace or delete and I can't cut, copy or paste. Every other application continues to function normally so it's isolated to VS2010. It's also only affecting the designer. If I hit the "Source" button/tab to go back to the HTML, everything returns to normal.
This happens on really basic pages. My pages have a master page but the master page and the normal pages only contain basic html tags and the odd ASP.NET textbox or button.
I do not know why that message shows, but as a workaround, perhaps just create a static htm page in your site, go to design mode, do you editing/formatting, then copy paste the source into the real file?
one guess for message is if there is some sort of data source on the page or in the master page?