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.
Related
hi I'm having troubles with the SharePoint list, I've got the list connected to a Visio, and when I'm on-premise, it update fast, I mean I change the list, click refresh in the Visio app and it's updated, but on the Visio web access from SharePoint, It takes too long, I can be pressing refresh, but its like it has a timer, every 2 or 3 minutes it updates, every change I do so far. The problem is that I need to be instant, sometimes its is instant because I luckily change the list when its about to refresh.
Is there any configuration in the server to me updates that fast?
English is not my native language, so I'm sorry
If you want your changes to be shown instantly, you can set Minimum Cache Age to zero in SharePoint:
http://technet.microsoft.com/en-us/library/ee524061.aspx
Note that default value (a few minutes) provides a better rendering performance in multiuser scenario.
Also note that this seetting does not seem to be available in SharePoint Online / Office 365 (please correct me if I am wrong).
I have a SharePoint 2010 Foundation site that has recently been upgraded from WSS 3.0. The upgrade was completed successfully with no glitches.
However, ever since I have upgraded the site I have got a problem relating to lookup fields on the NewForm.aspx (New list entry page) on some calendar lists that were existing on the site prior to the upgrade.
The issue is that I have two lookup fields, one for Client and another for Meeting Type / Location. When I am on the NewForm.aspx (new list item entry page) and I select an entry in one of the lookup fields the second doesn’t allow me to select anything and just gives me the top value in the lookup list without offering any other alternative selections like it should. These fields are just standard SharePoint Lookup fields and are not modified in any way, nor is the page. This problem does not happen on new lists I create (with more than one lookup field in them) in the site nor does it happen if I add extra lookup fields on the existing lists, it just leaves these two fields with issues.
I have used Internet Explorers debugging tools to see if there is an error in any of the JavaScript on the page but nothing is being reported as being a problem and I have also tried rendering the page in different standards in Internet Explorer to see if it is related to the browser but these do not many any difference. One thing that is apparent though is that the values for both lookup fields are being pulled in to the HTML of the page as I can see them when viewing the HTML source of the page when it has loaded and in the Developer Tools in Internet Explorer…
If anyone has any experience of things like this and could point me in the direction of a fix for this I would be very grateful...
Many thanks in advance...
Take a look at these two links. This first might be your issue and while the fix was included on August 2012 CU you still have to make a manual edit (not a true fix in my book)
http://support.microsoft.com/kb/2598273
http://support.microsoft.com/kb/2687375
When using the Ext.Lib Name Picker control connected to the NAB, the default is to view the first 50 entries from selected view (depending on whether groups/Persons is selected in property).
But there are no scroll/paging buttons on the dialog.
If I want to pick an entry from the NABPicker and the entry is after the first 50 I must use the Search button to find it.
Is this working as designed or a feature not yet added?
/Mike
You might be interested in using the viewpicklist control from openntf instead, link
It is very felxable, just set it to use the names.nsf and whichever view you need.
As far as I know this is working as designed. The server only returns a set number of entries so that the amount of data transfered when opening the Name Picker dialog box is kept nice and small, this way the dialog box opens faster.
You can increase the number of entries returned by increasing the maximum limits in the server document and internet site document and then increasing the maxRowCount attribute on the picker but you will seriously affect the performance of your application and it is not recommended.
Hopefully in a future release of the control they will add some sort of ajax based scroll similar to the inbox scroll in iNotes.
Mike:
I think the answer is "both". Working as designed and feature not added yet...
The Ext Lib is a open source initiative designed to support the simplistic Discussion, Team Room, and Document Library applications. The designers have limited experience with more complex applications and clearly limited exposure to large address books in their development arena.
The NAB pickers are a source a major disapointment to those of us trying to build larger scale applications. Perhaps at some point it will become a usable component but is is only marginally usable at this point.
/Newbs
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?
I need to count the page impressions of every page on a TYPO3 site into the db.
So I think I need an extension which is called on every page impression and increase a column 'impressions' in the db of the specific page.
I'm new to typo3 and new to extension development as well. Is there a way to include an extbase-extension on every page so some php-script get called?
(Update)
I want to add more information:
I don't need a counter which counts all PIs. The counter needs to be page-related. So it make sense to extend the pages-table from Typo3. Another need is that the extension should be done with extbase.
I'm new to typo3 and new to extension development as well. Is there a way to include an extbase-extension on every page so some php-script get called?
Once your plugin is configured you can include it with page.1234 < plugin.tx_yourextension_pi1 on any page. 1234 determines the position on your page.
The script should be USER_INT, so it's not being cached (mind you, this will cost loads of performance as previously stated by #norwebian)
As you don't want to output anything, make sure the controller stays empty as well.
Did you do a quick search in the extension repository? Trying a search for "page counter" reveals four relevant extensions.
"Sys_stat" is the closest thing to an "official" solution, it is really just enabling a few settings already existent. It has been reported to fill up the database with too much data, though.
"Generic Visitor Counter" would be my favourite, I believe (if I was going for a page counter at all), it is recently updated and seems simple enough.
You should really consider a proper stats extension, though. Both ics_awstats and ke_stats have been in my toolset.
YMMV. Be aware that if your site is popular, stats gathering quickly gets out of hand. On the other hand, if you go for a simple counter, including uncached extensions will cost performance.
I am not sure if I really understood what you want and need. After all, page impressions are not the same as page views. I wouldn't know the difference "onpage" right now though. So am I right in assuming that you mean page views?
If yes: I would take the following approach:
A separate, autonomous extension with a JavaScript for asynchronous calling of an API and a table for storing page views / page impressions.
Each page globally binds a JavaScript that initializes itself.
Once the DOM is ready, it sends a call to an AJAX API endpoint with the URL of the page as a parameter.
The endpoint takes only the URL.
For each unique URL, a record including counter is created or updated.
Extending the table for the pages doesn't make sense to me. What are you doing with a website that consists of news overviews, news details, press and blog sections, a dealer search and a store with product pages?
I would keep the statistics table standalone.
If you expand the table a bit and add date and time - no simple increment of hits - you can even identify the hottest pages of the week, the month, etc.
--
My approach won't increase/delay page load time much, if at all, and will have little noticeable impact even on heavily requested websites.
With the AJAX endpoint, it's then up to you how you deploy it and how much of the CMS framework you want to load.