I had a request for a form to count the number of days between two date pickers as one of it’s functions. All that you need to make this happen is add two date picker controls and one text field to display the count. I have included an InfoPath sample form that explains this in detail and should provide you with the knowledge to add something like this to one of your forms.
Have you ever logged on to your SharePoint site and the drop down navigation does not work? After days of clicking around, I decided to fix the issue, which really was not much of fix.
Turns out, this is an issue with my MS Office installation. All that you have to do is run a repair of your Office install under the add/remove programs area. Once the repair is complete, log back on to your SharePoint site and the menu should now appear.
I know that this may be common knowledge to most people in the IT world, but sometimes I forget even the simplest of tasks. I haven’t edited a hosts file in 7 years so it took me a minute or two to remember where I was supposed to do this. Now that I am running Windows 7, there is one more thing that I had to do…..Run as Administrator.
I decided to create a short video on how to edit your hosts file. Enjoy!
If you need to have more than one workflow for a particular list/library, DO NOT copy a SPD workflow and paste back into the same library.
What happens is that even if you change all of the properties of the files (names, etc.), there is still a hidden property that SharePoint likes to hold on to and uses to identify the workflow. Think of it as an ID.
Basically, you will have two different workflows with the same ID. When you publish one of these to a list/library, everything works fine. When you go to publish the second one, everything seems fine but after close evaluation, you will notice that the first workflow that you published is no longer attached to the list/library.
Moral of the story, don’t be lazy. Create a new workflow even if all of the information is the same.
Very often in InfoPath, I need to query Active Directory for certain pieces of information just so that I can have some type of functionality within my forms. One of the most used and easiest forms of this is the user profile service. I use this to my advantage to query e-mail addresses, user account info, etc. Also, this is a must if you use the Contact Selector control from within InfoPath.
Follow these steps and you will be on your way. Stay tuned for part 2 as I will be showing how to query the display name for AD accounts in a later post.
GetUserProfileByName Data Connection
Create a new data connection to “Receive Data” from “Web Service”.
Type in the following url: http://yoursite.com/_vti_bin/userprofileservice.asmx?wsdl
I was faced with this task recently. Let me paint the picture for you.
I have a document library with over 1,000 items in it. I added a new column (Named) that needs to have the same information as an existing column (Name). For whatever reason, the web part I am using for my list search does not recognize the existing column. I created a SP Designer workflow to copy the contents from the ‘Name’ to the ‘Named’ on creation or edit.
To do this, there are a couple of options.
The long drawn out option – Edit each file individually
The best option for me – Content and Structure
Power option – SharePoint Designer
I went with option 2 because I did not want to lag the server with a whole lot of who ha. Here are the steps I followed to make this happen.
Go to the site, Site Settings, Content and Structure
Expand the library to perform this action
Place a check into the ‘Select All’ check box
Click on the ‘Actions’ drop down and select ‘Check Out’
Once checked out (you may have to do this twice), click the ‘Actions’ drop down and select ‘Check In’
Make sure to check that you have performed this action for all items in your view. Mine were in groups of 100, which is generally the standard view. The fasted option for me would have been the SharePoint Designer route but I did not want to take a chance of checking out over 1,000 items at once and then check them back in. We already have enough load on the servers from all of the other users accessing SharePoint.
Have you ever seen this message before? Chances are, probably not but in my organization this might rear it’s ugly head from one time or another.
I received a call from one of my user’s and they said that they could not edit an Excel file from withing SharePoint. Since we have a mixed MS Office environment, I first verified what version of office was installed (2010). After that, I checked to see how my system performed (no issues). Then, I go through the process that most admins go through when troubleshooting; “Why is this working for me”, “What could it be”, “Maybe it’s just the user”, etc. Once that wears off, I sit back and think for a minute. Turns out, not a big issue at all, just a step left out in an upgrade process.
What happened was the user had Office 2003 installed on their computer and installed the compatibility pack to open newer versions. Eventually, the user upgraded to Office 2010. When this happened, the office compatibility pack was not installed, resulting in the error ‘The converter failed to save….’ blah blah blah.
The solution? Well, you guessed it…. Uninstall the compatibility pack. Simple. Done.
We had an issue come up about security with InfoPath forms. One of the major issues was that we could restrict items in the view, but if you used explorer view, all of the security would be bypassed. To counter this, we use a CEWP and the following jQuery script: HideViewsScript
Please note, you will need to change the first line in the script to reference your jQuery file:
Years ago, I setup an InfoPath form for an approval process. There are around 7 status changes during the duration of this form. We wanted to be able to see how long a request would take from creation to approval. This was actually pretty simple. All that you need is a calculated column. Follow these steps and you will be able to time an event/process.
Create Calculated Column (Form Duration)
Enter this for the formula: =TEXT(Modified-Created,”h:mm”)
That’s it! The calculation will look at the fields provided in the formula. The time will then calculate based on how long it took from creation to when it was last modified. If you have a form that hides a submit button based on a status, you will then be able to lock down the time calculation.