As developers know, SharePoint 2010 master pages can contain maximum 200 controls. I've searched arround a bit, but did not get any information or suggestion about this problem. Anyone faced with this problem before? I call this is a problem, because I need to put more than 200 controls. Do you have any suggestion about how to put 200+ controls in masterpage? Any trick, way, etc..
Have you checked the web.config? There is an entry for the user controls:
<SafeMode MaxControls="200" CallStack="true" DirectFileDependencies="20" TotalFileDependencies="50" AllowPageLevelTrace="false">
However I would not suggest changing it, because the limit of 200 exists for a reason. Actually a MS employee suggests you should split up your page into multiple smaller pages if you have more than 200 user controls: Need increase MaxControls value in web.config. Is there a recommended value?
Related
I am building a directory tool that will list entries for technical support contacts and listed by its appropriate company. My end goal is to allow end users to be presented with 2 simple inputs, a drop down with the list of companies and a text input to enter the name of the technical team they would like to reach. Sharepoint has made this a nightmare.
Since my server is on MSS 3.0 I decided to use a form webpart where I have added created the 2 input (dropdown and text input). I made the parameters to point to the input and added them to the filters and finally made the webpart connection.
I was able to get as far as making a sucessful filter for the technical team but as soon as I try to filter by client the results are very sporadic and mostly incorrect. I play around with the list filter in Sharepoint designer 2007 tried to group the filters together, tried changing the AND/OR in every possible setting but no luck.
Decided to push it by creating a column named blank that basically had empty values. The idea behind that was to allow end user to leave the technical team input blank and show all entries for the company. I thought somehow it would have maybe solve my sporadic issue but instead made it more complex.
At this point I can probably live without being able to search with blank results but I need to be able to at least filter by company and technical teams. At this point any sort of help is appreciated, been at this for a few weeks and my project is due last week so I am pretty much desperate to solve this problem.
For those that may have a similar problem I have found a work around to this problem. I decided to use the ASP.net User Control and this works much better than the form webpart and provides much better results.
Here a link that I found which help me get me on the track:
http://blogs.msdn.com/b/sharepointdesigner/archive/2007/03/05/asp-net-controls-filter-the-data-view.aspx
Is there a way to have user selected records remain selected as the pages are changed in the view? Currently, when changing pages in the view, the selection is lost.
For example, the user is looking at the Accounts entity, and wishes to select a few records from the first page of results and other records from subsequent pages.
I have explained that this is standard behaviour and that they should further filter their results but they are insisting that I try to find a solution.
There isn't a supported solution to your problem other than writing custom web-resource pages that will do exactly what you need.
I'm sure you've already told them to set their "records per page" to 250 in their Preferences.
In CRM 4.0, I once figured out where this "records per page" setting is stored in the database and I was able to change it to 5000 directly in the database. It did work (I think I had to iisreset as well), but it is obviously unsupported and could cause massive performance issues.
I have a basic knockoutjs project loading data from a SharePoint 2013 list scenario. Getting data and displaying data is easy, the problem that I'm running into is on the edit mode displaying the proper control. Everything should not be a textbox. This means the people picker control to dropdownmenus to calendar controls.
MSFT has some pretty good documentation on using the client side people picker control here"http://msdn.microsoft.com/en-us/library/office/jj713593.aspx
The problem that I have is calling this control inside my viewmodel.
Setting the value of the control doesn't look difficult courtesy of this blog post: http://www.sharepointcolumn.com/sp2013-setting-people-picker-value-in-newform-aspx/
I attempted to looking into computed values, but that doesn't seem to work. Does anyone have a blog post that I skipped over? The closest related post that I can find: http://yetanothersharepointblog.wordpress.com/2012/12/11/working-with-sharepoint-lookup-columns-in-knockout-js/
Lastly since it seems that I'm the only one doing this, does anyone think that I should not be reinventing the wheel with my forms and should just link each item to the appropriate SharePoint list item in edit or display view? I suppose that would be easier.
From a SharePoint Professional to another, I would highly recommend you to do that.
Just redirect the user to the item edit/display item page an let SharePoint take the leash of how to handle UI form elements.
Because, assume that you implement your custom form, what if the user decides to add one more site column to the list? Will you update your code to support another field?
From my personal experience with the beast I've come to the conclusion that structural implementation over already existent functionality tends to go wrong.
Also, if you have some kind of listing of items custom made and you want to provide editing, try to do something opening a pretty SP.UI.ModalDialog, its elegant and you use the sharepoint to do the work for you.
But it's just an advise.
I am facing problems with Refinement Panel in SharePoint 2010.
Please find below the issue:
Suppose we have Following refinement Custom Values as - Custom1, Custom2, Custom3, Custom4, Custom5. And then suppose Custom1-5 have things coming from Managed Properties.
I have uploaded adequate number of documents into the system. Now when I click on one of the values under Custom1 then filtering is done properly...and it shows Custom2, Custom3 if there are any document. I click on values under Custom2 and I could further drill down and get more specific results. All this is default functionality by SharePoint. I have not changed anything here.
But sometimes SharePoint is behaving strangely. If I click on one of the values under Custom3 (or Custom4, Custom5)...then all other filter options are gone. Only Custom3 and the value I clicked to select are shown. I know that the documents in this particular category have Managed Properties which exists under Custom1 and Custom2, yet those are not seen.
My client is after me saying that this is a bug, can anyone help me regarding the same. Am I doing something wrong is this is BUG/FEATURE by SharePoint. If it is a bug or feature please do share with me some document by Microsoft or others mentioning the same. I Googled a lot but could only find ways to use Managed Property etc with Refinement Panel.
Thanks.
Nitin
Its simple...just change the Threshold Value from 5 to 1. I did not know and wasted so much time running around. I hope this question may save some time for someone else.
We're working with a sharepoint 2007 site that has a number of dataview webparts showing different views of a document repositry. Each time we make even the most minor change (such as changing the chrome settings or adding a class) to the XSLT or webpart settings the DV webpart refuses to render.
Our XSL is vaild, as is the page the GUID is correct for the list and we are at a loss. We've resorted to editing the CAML files deleting and reimporting them which is obviously very slow. Any thoughts/ideas/help would be much appreciated.
I have faced this problem at our place too. Often I have found out that it is because of JS errors. Do you notice any errors on the IE? Did you try refershing the page by doing a CTRL+F5? I hope this helps, coz at times it does for me. I dont know the root cause and never cared to look into since it has happened only a few times.