Creating Calculated Columns using [Today] or [Me]
Calculated columns does not allow you to use [Today] or [Me] in the formula box. So how do we actually get the current date.
The solution I am going to provide is not 100% full proof, but it is a workaround for the problem.
1. Create a column called ‘Today’ in the list
2. It can be of any type – text, date etc.
3. In your calculated Column use [Today] as if you are using a SharePoint function
4. Now go and delete the Column called ‘Today’ which you created before.
Doing the above system, you are kind of fooling SharePoint and the calculated column you defined before will now reference to the Share Point [Today] function.
Problems you might see:
Calculated Column you created before might display you 30/12/1899 as the current date, but if you go back to the calculated column and hit ‘Ok’ again it should display the current date.
This is just a work around to the problem, if you wish to use [Today] in calculated columns.
Same steps goes for [Me] function as well.
You might use [Today] in calculated column like this:
=IF(AND([Due Date]< [CurrentDate], [Status]=”In progress”),”Overdue”, “None”)
SharePoint Designer 2007: Failed to load the workflow
When you open SharePoint Designer 2007 to create a new workflow, you get this error “Failed to load the workflow”
Solution One:
- Go to C:\Documents and Settings\<your user name>\Application Data\Microsoft\SharePoint Designer\ProxyAssemblyCache\(12.x.x.xxxx)
or
C:\users\<your user name>\Application Data\Microsoft\SharePoint Designer\ProxyAssemblyCache\(12.x.x.xxxx)
and delete 12.x.x.xxxx folder.
- Open SharePoint Designer again and it should work this time.
If it is still not working for you then try Solution Two:
- Change trust level in the .NET 2.0 Configuration (the MMC snap-in, found in Administrative Tools).
- Go to .NET Framework 2.0 Configuration > Runtime Security Policy.
- Choose “Adjust Zone Security” and change Local Intranet to “Full Trust”
It should now work at this point, if not
Go to Intranet options, pushed the slider up to full trust.
Someone might have posted about that but it’s good if this post can help few.
This InfoPath form template is browser-compatible, but it cannot be browser-enabled on the selected site
I was trying to publish InfoPath Form (browser enabled) to a SharePoint document library and got these errors.
This form template is browser-compatible, but it cannot be browser-enabled on the selected site. This may be caused by one of the following reasons:
- The server is not running InfoPath Forms Services.
- The necessary features are not available on the site collection.
- They policy setting on the server does not allow users to browser-enable form templates.
I Checked
- all features were running on sitecollection level and at site level
But here is the solution, i do not why it worked but it did work.
Although you can activate and deactivate Office SharePoint Server Enterprise Site Collection features , Office SharePoint Server Enterprise Site features through site collection features and site features. But give it a try through STSADM
Solution:
stsadm -o deactivatefeature -filename IPFSSiteFeatures\feature.xml -force -url %SITE_COLLECTION_URL%
stsadm -o deactivatefeature -filename IPFSWebFeatures\feature.xml -force -url %SITE_COLLECTION_URL%
STSADM.EXE -o activatefeature -filename IPFSSiteFeatures\feature.xml -url %Sitecollection_URL% -force
STSADM.EXE -o activatefeature -filename IPFSWebFeatures\feature.xml -url %sitecollection_URL% -force
*NOTE: The “%Sitecollection_URL%” is a place holder that would be replaced with your site collection URL, such as: http://sharepoint/sitecollection
MCTS – Microsoft SharePoint Server 2007 (Configuration)
I have recently passed MCTS (70-630) exam for Microsoft SharePoint Server 2007 – Configuration with 964 marks.
Installing Template using STSADM command
Sharepoint Admin can goto command line and run stsadm.exe or you can find this utility under
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\Bin
Goto the command prompt and got the above location
run STSADM.EXE -o installfeature -filename YourFeatureFolder\feature.xml
Make sure that the feature is not already installed. If it is than deactivate it and uninstall it.
make sure that your assembly is signed and also installed into GAC. When installing assemblies into GAC it would be great to restart IIS.
