I'm using Visual Studio Professional 2019 to build SSRS reports
I customize the parameters pane and it previews fine but for two reports but when one of them is published it changes
I have one report with the parameters panel customized, it has four columns and looks something like this
Example of parameter pane layout for report that works when published
When I publish the report the layout of the parameter panel stays the same
I have another report with a similar layout, which looks something like this
Example of parameter pane layout for report that doesn't work when published
When I preview the report locally the layout of the parameter panel stays the same:
However
When I publish the report it changes.
On the published report it looks like this
Example of parameter pane layout on report that does not work when published
The parameters are no longer flush with one another (there is space between them) and the number of characters in any line of the parameter description is reduced to that
[Example parameter Description1] [dropdown box] [Example parameter Description 2][dropdown box]
becomes
[Example [Example
parameter [dropdown box] parameter [dropdown box]
Description 1] Description 2]
It takes up a lot of space and looks rather messy.
Server is
Windows Server 2019
With
SQL Server Developer
Product Version 15.0.1102.897
Local PC is
Windows 10 Pro
Related
I use MaterialList library to display card views and in some projects each card view has extra space after it (I cannot post a picture since I need 10 reputation...). Any idea why?
Update
The above occures when I am running the library's sample code from within my application. Everything is ok when running the sample code as is (I made no changes to the sample code in order to run it from within my application).
I have created a custom content type ContactForm and I'm using the Custom Forms module.
Is there a way to override the Create.cshtml file only for the ContactForm?
I tried Create-ContactForm.cshtml but it's not working.
If you want alternate view to be displayed follow the steps.
1. Enable Designer tools module.
2. View the page where create.cshtml is displayed.
3. You will see see small minus sign in right bottom corner, click it to enable shape tracing.
4. Trace the shape for which you want alternate view.
5. check shapes tab, there will be multiple alternate options availbale. click on create for appropriate one.
6. find and edit that template in visual studio.
first of all read about alternates and shape tracing.
some reference for you.
http://devhammer.net/blog/Customize-Orchard-CMS-with-Designer-Tools
http://docs.orchardproject.net/Documentation/Alternates
When creating a very simple report containing only a textbox, I am able to put an action to that textbox in SSRS to make the textbox clickable:
When previewing the report in the SSDT preview pane, the textbox is clickable as expected:
However, as soon as I upload the report to Sharepoint and view it in a browser, only the text inside the cell is clickable (instead of the entire cell):
Changing compatibility views, using different browsers doesn't change anything.
Is there any way to make the entire cell clickable when viewing my reports in Sharepoint (2013) too?
(Maybe a setting I'm missing with which to make the rendering of Sharepoint SSRS the same as SSDT or Report Viewer rendering?)
No, this is not possible in SSRS with text.
A possible work around, assuming the text is static, is to use an image in your cell and attach the action to the image.
Reason for this occurring:
On the web:
When reports are viewed on the web through SSRS in remote mode, they ultimately get converted to HTML. Textboxes get converted to a <div> tag. A textbox with an action gets rendered as a <div> tag containing an <a> tag. As a result, when viewed in the web, your browser interprets the text as regular hyperlink in a <div> instead of "textbox" object. Due to the implementation of <a> in HTML, only the text is actionable, not the entire box. This can be proven by rendering the report in your browser and inspecting the element.
One possible reason it works this way, is that in plain HTML (before v5) it isn't correct to put a complete DIV inside an anchor tag (see this discussion for more about that). Making the text inside an anchor-tag display like a block (via CSS) would be correct, but IE7 (the compatibility mode reports are rendered in by default) isn't that good at working with the CSS display: block statement :).
In SSDT:
In SSDT, the report is executing using the WinForms ReportViewer. What this means is that the Preview screen will also use WinForms controls to build the preview. As a result, a textbox in this case will be represented by the WinForms control TextBox object. This object's actionable area is not just the text but the entire bounds of the object.
limit number of characters entered in cognos search and select prompt
`The below script works for text box.
<script>
// The ASDF here comes from the Name property of the prompt
var fW = (typeof getFormWarpRequest == "function" ? getFormWarpRequest() :
document.forms["formWarpRequest"]);
fW._textEditBoxASDF.maxLength = 3;
</script>`
I need a similiar piece of code to work with Search and select prompt.
I don't have cognos in front of me but let me tell you how i did stuff like this with Javascript. Please read entirely as there are several approaches.
Put a uniquely named/id DIV tag around your native Cognos select and search prompt(The one your typing in. This will make it easy to reference with Java's dom model for the next steps. We will eventually make this default search prompt invisible/hidden but for now keep it visible until the following steps are coded/debugged.
Create an HTML control in the simliar style as the native Select and search with the proper max-length settings that you want. Use the text box on change event to update the native Cognos select and search prompt. for debugging troubleshooting i find it handy to have javascript alert the DIV innerHTML so you can see whats under the hood with the Cognos control. Sometimes i uses this innerHTML as the starting point for my "Cloned/Shadow" HTML prompt that i have control over.
Once you have your new HTML control effectively changing the Cognos control you can make it invisible.
On complex dashboards/scorecarding i wrote routines to clone cognos prompts and expose their HTML so i could create my own control that would quietly manipulate the actual hidden controls. This gave me complete control over presentation and functionality.
There are many variations on this once you have the controls innerhtml like replacing the innerHTML with one of your own immediately after the page loads that has the restrictions on length. Or simply seeing if you can massage the property learning from the innerhtml.
In Cognos 8.4 and 10 there is a new method to dynamically add a method to a control to be called prior to any other methods. It is tricky but it is on IBM's web site. I may be more cleanly implemented in 10 and also IBM is not shy about showing off these solutions on their web site.
We are using coded ui test using visual studio 2010.We are testing .Net 4.0 windows application.
Here is an scenario.
We have an windows app which has a button named submit and we have recorded a workflow which clicks on submit.
Now when we generate code using coded ui the serach criteria for the button is based on its name (display name of button).
If tommorrow developer changes the button's text to submit1 , our scripts fail.
We tried using "controlName"[name given to the control and not the display name] property in search criteria instead of Name , but it does not work.
We get following error - "The playback failed to find the control with the given search properties"
Related problem happens to me also. I solved it by sending the Focus to the UI control before using that control.
Try this.
this.UIAssettePresentationsWindow2.UINOWindow.UINOButton.SetFocus();