We have a performancepoint services Business intelligence site, in this we dont need quicklaunch and top link bar for dashboards, so i have done this by adding the script in the content editor and hiding it, after doing this the quicklaunch/left navigation and top link bar have been hidden/removed. But when published the dashboards back to sharepoint site the left navigation and top link bar reset/unhidden.
Please suggest me how to make them hidden permanently even we do publishing the dashboards.
Thanks
If you have a PerformancePoint dashboard, you can add webparts inside of it. It sounds like you have done this by adding a webpart with custom css to hide those elements.
The problem with doing this is when you edit that dashboard PerformancePoint can take hold of that page and relay the webparts. Thus your webpart is no longer included in that page.
One option is editing your PerformancePoint site's masterpage or css for that site to remove those elements.
Another option would be to a stand alone webpart page within that site and deploy your PerformancePoint Content as individual web parts on the page. In my experience this becomes painful when you use lots of connected filters, since you will have to manually wire them up.
Related
I have a VB10 app that uses panels, one for menu, one for main screen and then i want to add one for a breadcrumb menu. I use user controls to display in pnlMain and would like the breadcrumb trail to add an link with user control info every time I add a screen to pnlmain...and remove the link when I click on the previous link.
I would like to build the links dynamically like they do here: http://www.codeproject.com/Articles/17714/Create-a-Breadcrumb-Menu-in-VB-NET-WinForms,
but I couldnt get the links to display when I ran the solution.
and if I get the links to show, how do I associate the user control to that link?
Thank you for your help. The breadcrumb shouldnt go more than 3-4 levels deep
I am trying to find the difference between the uses of a basic page and a blank page on windows store apps. I am writing an application that has multiple pages and I am not sure which one to use for my main page and I can't seem to find an answer that is helpful.
Basic Page inherits Common.LayoutAwarePage. This gives your page various capabilities like the automatic back button and a visualstatemanager for snapping among other things.
Blank Page only inherits Page and does not get any of the above capabilities. So for example if you need to incorporate snapped view in your page, you need to add a handler for the size changed event in your code.
A Basic Page makes it very easy to just write all the snapped changes in your VisualStateManager in XAML and then test it without running your code using just the device tab where you can select state of your device.
The MainPage in your project is a Blank Page and I prefer to create all other pages as Basic Pages to not worry about stuff like the back button.
That being said, Windows 8.1 apps do not include the LayoutAwarePage so if you are not used to the LayoutAwarePage, do not bother.
Let me know if you need more clarification.
Go with the Basic Page as it gives you automatic back button your view's title etc, and if you don't need them you can disable them also. But for blank page you have to write code for those common things.
This blog post will help you in understanding of Basic Page vs Blank Page.
http://myblogwindow8.blogspot.com/2013/06/blank-page-vs-basic-page-template.html
I created a web part and deployed it. I want to display only webpart data. I dont want to display toolbar which allow minimize, close and edit web part & title , i did set Chrome Type=None . but its not working. How can i make web part as non-configurable to users means user can see it. not configure it.
thanks
This is depend on privileges. Where you administrator you will see every web part options, but if you a anonymous user can see only title if you not set as chrome.
I've built a WebPart for a SharePoint 2010 site. I need to add it to one of its master pages (using SharePoint Designer), and when I select it from the WebParts menu I click it but I don't see it added on the design page...
Could you please tell me how to do it?
Thanks in advance!
Brian
Typically, the Web parts get added to Pages (in a Web Part Zone) not the master page. You can force this by entering Advanced Edit mode in SPD and add a Web Part Zone & Web Part but it is not the way in which Master Pages were intended to be used.
I've built a web part for SharePoint 2010.
Using SharePoint Designer I've got it to work on every page within the site, but then I realized that I only want it to work when users navigate document libraries.
Is there any way to do that? If not, how can I check that condition from the web part?
Using SharePoint Designer I've got it
to work on every page within the site
Does this mean you have embedded it in the master page?
A quick and dirty way; you could check the url for /Forms/ and only show it then.