Dynamics CRM report rendering issue (open up in a new tab) - dynamics-crm

If i open an report in CRM 2015 with "run Report on selected report" the following happens:
report dialog window appears (loading)
new browser tab opens
report load into the new browser tab
report dialog window is still loading (endless)
So my problem is, that the Report renders in a new tab istead of the dialog window, but why?
Screenshot from new Tab & Dialog:

Related

How to fix background.js is not being invoked in firefox addon development? [duplicate]

I am trying to test sample code for web extension for browsers.
But, it doesn't work. I checked the console for Google Chrome and also for Firefox. It doesn't print anything. The following is my code:
manifest.json:
{
"description": "Demonstrating webRequests",
"manifest_version": 2,
"name": "webRequest-demo",
"version": "1.0",
"permissions": [
"webRequest"
],
"background": {
"scripts": ["background.js"]
}
}
background.js:
function logURL(requestDetails) {
console.log("Loading: " + requestDetails.url);
}
chrome.webRequest.onBeforeRequest.addListener(
logURL,
{urls: ["<all_urls>"]}
);
console.log("Hell o extension background script executed");
Am I missing something?
Your code is correct as written, it works and outputs to console.
If you are not seeing it, then you are, probably, looking at the wrong console.
1. Firefox
Mozilla describes what extension output can be seen in which console in their Debugging article.
Browser Console
The Browser Console no longer shows output from WebExtensions background pages by default. You can have it show output from all WebExtensions by selecting to display "Show Content Messages", which is available from the popup that opens when you click on the gear-like symbol "⚙️" in the upper right of the window, just to the right of "Requests". Depending on what you are doing, the Browser Console may show output from a WebExtensions Experiment. You can access the Browser Console from Tools➜Web Developer➜Browser Console (keyboard shortcut Ctrl-Shift-J, or Cmd-Shift-J on Mac).
In older versions of Firefox, this was the console to use to see output from extensions. However, that is no longer the case.
Browser Toolbox
If you have it enabled, you could also use the Browser Toolbox console. You can access it from Tools➜Web Developer➜Browser Toolbox (keyboard shortcut Ctrl-Alt-Shift-I; On a Mac: Cmd-Alt-Shift-I). If it is not available you can enable it through options from the Web Console settings page.
The console in this toolbox will show output from both scripts running in the background context and from content scripts. However, complex data will not be available (e.g. no Objects).
Add-on Debugger
This is what you should be using to view console output from scripts running in the background context of your WebExtension. This includes background scripts, scripts running in popups, options pages, and any other page loaded from the extension as the main URL for a tab, or iframe. You can access the Add-on Debugger though about:debugging➞Inspect (use the "Inspect" button that's associated with the WebExtension you are debugging; there's a separate button for each extension). This will open a new tab with the debugger. You can then click on the Console tab within that browser tab. This console will display only content from the WebExtension which you are inspecting.
Web Console
You, probably, are looking at the Web Console (keyboard shortcut F12) which is associated with only a single tab. This is what you want when debugging a webpage, but not an add-on's background scripts. For a content script which is injected in that tab, the console.log() output will show up in this console. However, you will not see output from any other portion of your add-on (e.g. not content scripts in other tabs, not background scripts, etc.).
2. Google Chrome
Showing the correct console for your extension is a bit more complex in Chrome. Console output will show up in only one of multiple possible places, depending on from what context the console.log() was executed. Each of the following DevTools are independent of each other and are displayed in separate windows, or tabs. Displaying in the associated tab (bottom or side) is the default for the DevTools associated with web pages and content scripts, because those are specific to the tab. For the web page/content script DevTools, you have the option of having it displayed in its own separate window, or docked inside the tab (side or bottom).
Background Scripts
As explained here, you have to go through multiple selections on a drop-down menu, to get to the chrome://extensions page (or you can type that in by hand as the URL, or use a bookmark) then select both a checkbox ("Developer mode") and then click on the "background page" link. Then, you have to select the "Console" tab on the window that pops up.
It is much easier to show what you have to do:
Content Scripts
Output will be shown in the regular web console (in the web Developer Tools). You can open it by pressing F12 (or other shortcuts) in the webpage in which your content script was injected. Each web console will only show the output from the scripts injected in that tab.
Doing the above with show the console.* output from your extension, but will result in the console JavaScript command line, debugger, etc. being in the context of the page, not the content script.
If you want to use the console JavaScript command line in the context of the content scripts which are injected into a web page, you need to select your extension's content script context from the drop-down menu in the upper left of the Console window. This drop-down menu will normally start with the value "top". The drop down will have selections for each of the content script contexts (one per extension that has script(s) injected).
Popup (built-in)
Right-click on your browserAction button and select "Inspect Popup". Alternatively, right-click within the popup and select "Inspect". Either will open the DevTools for the popup page. The popup will be kept open under more conditions than it normally would, but will still be closed if you switch tabs, etc.
Options
Right-click within the main content of the Options popup (not the title bar) and select "Inspect". This will open the DevTools for the options page.
Devtools extension panel
Same as Options above: right-click inside + inspect.
In case your panel intercepts the right-click or in a bugged Chrome 97/98, open devtools-on-devtools, then use its picker button in the toolbar of the Elements panel (or press Ctrl-Shift-C on PC) to select your panel in the original devtools window.
Tab or popup (detached) with a page from your extension
When a tab or a detached popup window is focused, you can open the DevTools by pressing F12 (or other shortcuts), or by opening the context menu (right-click) and selecting "Inspect".
Note, the "detached popup" here means a window without an address bar, which is created using window.open or chrome.windows.create. There was another type called "panels", but it's no longer supported in modern Chrome.
Which console are you viewing in for the logs?
If you are viewing console on a tab, then that is the wrong place.
Open settings / Extensions or in a new tab type
chrome://extensions
Under your extension click on "background page" link which is where you can watch for logs
**Make sure Developer mode is checked
Yes for Chrome you have to click the background page link mentioned, but it won't be there unless you set it to be persistent:
"background": {
"persistent": true,
"scripts": ["background.js"]
}

SSRS Export to Excel

I have a SSRS report with Hyperlinks to 2 other SSRS report, through the Actions tab I am passing a parameter value to those hyperlinks, main report is exported to Excel and link is there everything is fine.
"=http://[SERVER]/[RSSERVER]/Pages/ReportViewer.aspx?[REPORTName]&rs:FORMAT=EXCEL&[ParemterName]=" &[ParameterValue]
When I myself click any of the hyperlink after exporting the report in Excel it opens a browser window and downloads (in my Download folder) the linked rdl in excel format with its actual rdl name .XLS and that's the expected correct operation without giving me any security warning in Excel and I can click on other hyperlink to other report.
But for all other users when they click the hyperlink first they receive a security warning about opening a harmful link and when user clicks OK it opens the link but the filename is ReportViewer.XLS so if user do not close that file and click on other hyperlink it will not download it because ReportViewer.XLS is already opened.
I have checked with couple of users their Excel Options are identical to mine.
I am not sure what is the causing this issue.
Thanks,

Vsto Addin to show on home tab

I have created a vsto Addin where I want to show a Ribbon control on Inbox window and when the user clicks reply in same window(not in pop out window).
I was able to set the addin to load on Outlook compose and reply pop out windows.
I tried to set the property controlId as TabMail and selected RibbonType property (selected everything, just tried hopping one of those will work )
Any one have a solution
Do you get any Ribbon UI errors?
By default, if an VSTO Add-in attempts to manipulate the Microsoft Office user interface (UI) and fails, no error message is displayed. However, you can configure Microsoft Office applications to display messages for errors that relate to the UI. You can use these messages to help determine why a custom Ribbon does not appear, or why a Ribbon appears but no controls appear.
To show VSTO Add-in user interface errors
1. Start the application.
2. Click the File tab.
3. Click Options.
4. In the categories pane, click Advanced.
5. In the details pane, select Show VSTO Add-in user interface errors, and then click OK.
For Outlook, the Show VSTO Add-in user interface errors checkbox is located in the Developer section of the details pane. For other applications, the checkbox is located in the General section of the details pane.
Most probably the TabMail id doesn't exist in all contexts and you get an UI error. So, a custom UI is not shown finally. Am I right?

Outlook addin custom pop up form

i am creating an addin for outlook . i am stuck with my requirements ... how to open a pop up for entering some input value on click of custom button in ribbon.
i.e How to open a form in outlook UI
simple question it was ..
i am able to open vb form ..
NativeAddIn::ApplicationConfiguration ^appConfigurationform = gcnew NativeAddIn::ApplicationConfiguration();
appConfigurationform->ShowDialog();
To create a ribbon in the outlook
Click on file - go to options - customize ribbon - create a new tab - rename it by clicking on it next drag an action to be performed on the particular ribbon
and import settings
click ok
close the outllok and reopen it again
this is for outlook application 2019.

Why can't I see the "Report Data" window when creating reports?

I'm creating RDLC reports in VS10. When the program is NOT running, I can see the toolbox, and add controls to the report, but the "Report Data" pane is nowhere to be found, so I can't fill the controls on my report. However, if I run the solution, the "Report Data" pane appears, and I can drag fields on to my report, however the Toolbox contains no controls while I'm running. So, I've had to put the controls on to my report while not running, run the project and while it's running I can put the fields in....
anyways, how do I get the Report Data pane to stay visible while the project is not running?
The most common answer to this problem is to go to the Data menu and choose Show Data Sources. This option does not appear for me.
The Show Report Data Pane keyboard shortcut did work for me:
CTRL+ALT+D. There is nothing in the menus that I could find that does this same thing.
After I accidentally closed this window, I took an hour to find how to bring it back up.
The right answer is indeed:
View-->Report Data (ctrl+alt+D)
The tricky part: the 'Report Data' entry does not always appear in the 'View' dropdown. Make sure that you have a report open, and some element of the report selected.
If you're not 'in the report', the entry disappears from the menu.
Hi I faced the same issue in VS2008, I tried based on the post 8 (Thanks to the "Tricky part" section in that)
The (Ctrl+Alt+D) combo did not work there in VS2008, but after opening the Report file(rdlc) I browsed on the View menu and found out that View->Toolbars->Data Design is the solution for that.
Upon opening that we get around 4 icons of which the "Show Data Sources" section brings the "Website Data Sources" section which fetches all Entities, Typed DataSets etc.
The keybord shortcut is (Shift+Alt+D).
The twisty part here is the "Data Sources" section available with the Server Explorer toolbar doesnt bring up any stuff but the "Website Data Sources" brings all the needed., can somebody explain that to me.
I was also same problem in Visual Studio 2013, Then Suddenly got an Idea.. Click on Report to make focus on it.
Simple Press Alt+Ctrl+D
I had the same problem, but in c# 2012
I closed the "report data" and I couldn't find it and I finally found a solution to this issue.
This is my method:
VIEW >> TOOLBARS >> CUSTOMIZE >> COMMANDS ... select from the "Menu bar" .. VIEW.
OK now in the "Controls" find the "REPORT DATA", select it and MOVE it UP, close the menu.
After that select a file.rdlc and click on the "View" ... OK Finally will be appeared "REPORT DATA"...
I had to go through a bit more to force a refresh in VS 2008.
First, there is a Data Sources pane/toolbox (menu trail = Data > Show Data Sources), and a Report Data Sources dialog (menu trail = Report > Data Sources). I had trouble with the Data Sources pane reverting to an earlier property list every time I opened a certain report; it was as if the report designer was overwriting the data definition with the report's cached version thereof.
To remedy this, I had to:
Exclude the report from my project to stop the build errors
Clean & rebuild my project
Refresh the Data Sources pane & confirm I could see the new fields
Re-include the report and open the report designer with the Data Sources pane pinned in view
(This is the key) Drag one of the new fields anywhere onto the report surface
Number 5 forced the report's internal XML copy of the data definition to refresh. Immediately after that, I could build again.
If the report designer is opened, Report Data Pane can be enabled using view menu.
View -> Report Data
It is in visual studio. In the designer page, it is on in the menu bar, there is XTRAREPORTS field. You can show up panels using it
Open report in Report designer
Go to View menu -> Report data
I was in a weird situation in VS2019 where choosing View -> Report Data did nothing, and pressing Ctrl-Alt-D did nothing. The Report Data window had just strangely appeared on the left for no reason, when it was supposed to be on the right, and so I had moved it back to the right and then made it auto-hide. Not long after that it disappeared and would refuse to reappear. Possibly it was off-screen but hard to say.
To fix, I had to resort to using Window -> Reset Window Layout which restored its position and I was able to use it again.
First of all select report file with rdlc extension and then go to View > Report Data
please go to
View > Toolbars > Customize
then select "Data" categories then click "Show data source" in command panel
"Data" menu will be seen in menu panel. click to get the website data source

Resources