|
|
Update: Marc D. Anderson has now updated the Jquery files, so if you use the latest version this won’t be an issue anymore and you can disregard this post.
I have previously written a walk-through about how to implement a relationship between two columns:
http://www.uccorner.com/54/sharepoint/cascading-drop-down/
My friend and excellent SharePoint-er Jasmine Garry found ut that under certain circumstances, this approach did not work. To be more precise, if your site is in another language than English, and your column in the list where the relationship is (i.e. “Vacation Plans”) allows for multiple select, you get this error:
Message: Column not found on page
The reason for this is that the Jquery file uses hard-coded English terms to create a string that works with multiple select.
Solution:
First, in the code for your custom NewForm (the page where you are getting the actual error), look for a select tag and find the one where title=”City possible values”. Possible values will be in your own language. Now open the jquery.SPServices-0.4.8.min.js-file (or the version you are using), replace all occurrences (there are several) of possible values with the equivalent from your own language that you just found in the source code for the page.
Now, do the same procedure for “selected values” and you are good to go.
This is a workaround, and is expected to be fixed in a later release of the Jquery file by Marc D. Anderson.
Thanks to Jasmine Garry and Marc D. Anderson for figuring this out: http://spservices.codeplex.com/Thread/View.aspx?ThreadId=85478
Recently there was a request to rename a server running Sharepoint 2010 Beta (Could just as well have been MOSS 2007 / WSS 3.0 though). This server was running SQL on the same box, but the solution here can do the trick for many renaming issues.
So what happens when you rename your server and gives it a new hostname? Well, Sharepoint doesn’t like it. This is the message I got:
Cannot connect to the configuration database.
Oops. That’s a message you do NOT want to see.
So you try to enter Central Admininistration and get “Internet Explorer cannot display the webpage”. Well, as soon as you take a look in the address field in the browser, you see why: the shortcut pointing to Central Administration points to the wrong URL (e.g. oldservername:10000, not newservername:10000, assuming Central Admin runs on port 10000). So you type newserver:10000 and cross your fingers. Sorry, you get the same “Cannot connect to configuration database”.
But fear not, you can fix this! First of all, rename your server back to the old server name and restart, and everything will work again (you can take a deep breath now). But you still want to rename the server, right?
Solution
You have to reconfigure Sharepoint and tell it where it can find the databases. If you already have renamed the server, you can probably do the same thing as described below, but the best is to do this in advance. Besides, nothing works anyway right, so reverting the name temporary with the required restart won’t do any harm and give you time to the aforementioned deep breath. (If you try to fix this with adding an entry with the old server name in your host file, you’ll just get “An unexpected error has occured” or the same “Cannot connect to the configuration database”).
This is what you do:
- Run this stsadm command: stsadm -o renameserver -oldservername oldservername -newservername newservername.
- Rename and reboot server.
- Enter Central Admin and look over all your Alternate Access Mappings (you’ll have to change to the new server name everywhere the old server name still shows).
- I didn’t have this problem with 2010, but you might have to check and possibly reset your site collection admins. I wouldn’t be surprised if you’ll have to go over your host names in IIS in case you are using host headers also.
The request for Cascading Drop Down, filtered drop down, dependent drop down or what you call them is one of the most common requirements from customers. This rather basic functionality is surprisingly not implemented in either WSS 3.0 or MOSS 2007.
What is Cascading Drop Down?
You have two columns in your Sharepoint list, Country and City. Both are lookup/drop down columns. When you choose a country in the Country Drop Down, you only want to see the cities in this country available in the City Drop Down column. This of course makes life easier for the end user, and improves data quality.
Solutions en masse
There are however lots of solutions for this. Datacogs’ Cascading Drop Down is well-known, and various improved versions like SharePoint Cascading Drop Down List (With Filter) Field Type and Query Based Lookup Field Control (Custom field controls), both on Codeplex. These are all free, you can also find solutions out there you have to pay for. I have tried several of these, however good work these guys are doing making this for free, there are som issues that keeps me from using them, like annoying page refresh, creating lots of versions of the list element and the general problems you can get with restore/moving/upgrading data that is not standard Sharepoint.
The solution
Instead, I have used this solution with success. The list is still standard Sharepoint, which gives great flexibility and stability. This way, the filtering is done in the forms for creating and editing elements. Because of this, you don’t even have access to the server to implement this. I have used this solution both in document libraries and in regular Sharepoint lists. Continue reading →
Ok, this is a simple question really.You have a links list, and want the links to open in a new window. Not really best practise, but a common request for external links. (Best practise is of course to let the user decide – just hold down Shift while clicking the link and it opens in a new window).
The answer can be simple or a little more advanced, depending on how you solve it:
1.#openinnewwindow
To add #openinnewwindow to the end of the URL is a common suggestion, but it doesn’t work unless you make some JavaScript modifications.
2. Summary Links Web Part
Using MOSS, you say? Well, let the Summary Links Web Part come to the rescue. This web part is included in MOSS. Add this web part to a page and you can easily customze the links.
The drawback is that you add and edit the links in the web parts itself, it’s not connected to a list – not the Sharepoint way to do it if you ask me. You’ll have to have Design or Contribute permissions to add links that everyone can see.
3. Convert to XSLT Data View
OK, you only have WSS but you have Sharepoint Designer? Well, just open the page where you have a web part showing links from you links list in Sharepoint Designer.
Right-click – Convert to XSLT Data View.
Now you can right-click a link and set the target to a new window.
Continue reading →
|
|
