One of our user was creating Survey in Sharepoint and when he tried to embed the survey entry url in the email to be sent to entire company, the url got truncated in the email send.
The workaround is to shorten the SharePoint url.
In our case we couldn't use Alternate Access Mapping and create separate url.
So the workaround was to shorten the url using NewForm.aspx-
http://abc.com/xyz/list/mysurvey/NewForm.aspx?Source=http%3A%2F%2Fabc%2Ecom%2Fxyz%2Flist%2Fmysurvey%2FAllItems%2Easpx
to http://abc.com/xyz/list/mysurvey/NewForm.aspx
Tuesday, January 26, 2010
Monday, November 16, 2009
How to do a SharePoint project
Refn: http://sharepoint.mindsharpblogs.com/Bill/archive/2009/10/08/What-Does-It-Take-to-Implement-a-Company[dash]Wide-Taxonomy[ques].aspx
Following article is by Bill English.
In my(Bill's) mind, the first place to start is strong set of business requirements that outlines what you want the taxonomy effort to achieve. In every company I've worked with, this has been lacking. With the lacking of a clear outline of the problems that need to be resolved, it's tough to know what success looks like and even more difficult to gain champion and grassroots support. So, the place to start is to ensure you have clearly defined business requirements that management has approved and can (and will) support.
What else needs to happen?
At a minimum, you'll need to work towards these goals:
Need to get a single-version of the truth by eliminating outdated or redundant data
Need to tag information with meaningful data that is highly discriminative
Need to train users to use the input and findability tools plus their metadata
Need to change the culture to get everyone on the same page because this represents serious culture, business process and information management changes
Need to develop document-type lifecycles that specifies the following:
********************************
-----------------------------
Document Type Content Owner Security Level Repository Recoverability Tool(s) Education Policies Metadata(Descriptors) Workflow ConsumingAudience ContentType
----------------------------------
Envision
Creation
Consumption
Retention
Archival
Disposition
********************************
Every company addresses these elements in a different way and in a different order, but essentially, you're connecting the following:
How information goes into the system (Putability)
How information comes out of the system (Findability)
What tools are needed for both
Taxonomies
Document Life Cycles
Let me emphasize that organizing information in SharePoint is directly connected to organizing information in your organization. This is *always* a business process, information management question before it is a technology question.
Following article is by Bill English.
In my(Bill's) mind, the first place to start is strong set of business requirements that outlines what you want the taxonomy effort to achieve. In every company I've worked with, this has been lacking. With the lacking of a clear outline of the problems that need to be resolved, it's tough to know what success looks like and even more difficult to gain champion and grassroots support. So, the place to start is to ensure you have clearly defined business requirements that management has approved and can (and will) support.
What else needs to happen?
At a minimum, you'll need to work towards these goals:
Need to get a single-version of the truth by eliminating outdated or redundant data
Need to tag information with meaningful data that is highly discriminative
Need to train users to use the input and findability tools plus their metadata
Need to change the culture to get everyone on the same page because this represents serious culture, business process and information management changes
Need to develop document-type lifecycles that specifies the following:
********************************
-----------------------------
Document Type Content Owner Security Level Repository Recoverability Tool(s) Education Policies Metadata(Descriptors) Workflow ConsumingAudience ContentType
----------------------------------
Envision
Creation
Consumption
Retention
Archival
Disposition
********************************
Every company addresses these elements in a different way and in a different order, but essentially, you're connecting the following:
How information goes into the system (Putability)
How information comes out of the system (Findability)
What tools are needed for both
Taxonomies
Document Life Cycles
Let me emphasize that organizing information in SharePoint is directly connected to organizing information in your organization. This is *always* a business process, information management question before it is a technology question.
Sharepoint site typical tasks or project items
Refn: http://www.shareesblog.com/?p=213
This is your “get started” list that you should incorporate into your project timeline.
Document libraries and lists
Analyze document usage
Plan document libraries
Plan lists
Plan enterprise content storage
Site Navigation
Metadata
Content types
Information management policies (Labels, Barcodes, Auditing, Expiration)
Records management
Moving content
Plan content deployment
Workflows
Site Templates
Working with site templates and definitions
Content approval
Versioning
Check-outs
Standardization across sites
People and groups (permissions)
This is your “get started” list that you should incorporate into your project timeline.
Document libraries and lists
Analyze document usage
Plan document libraries
Plan lists
Plan enterprise content storage
Site Navigation
Metadata
Content types
Information management policies (Labels, Barcodes, Auditing, Expiration)
Records management
Moving content
Plan content deployment
Workflows
Site Templates
Working with site templates and definitions
Content approval
Versioning
Check-outs
Standardization across sites
People and groups (permissions)
Wednesday, November 4, 2009
Error Opening Excel 2007 xlsx in Sharepoint
Problem: With no excel services enabled, users cannot open the xlsx in excel - it opens in browser and they get "web access error".
Soln:
The library should be set with "open in client app".
Soln:
The library should be set with "open in client app".
Wednesday, October 28, 2009
IE crashes on checking out or editing documents or Excel files in Sharepoint MOSS
Issue: If you are using a combination of Office 2003 and the 2007, then users will have problem with Checkout and Check-in SharePoint files.
Resolution:
1) Install hotfix 938888.
2) Repair Office 2007.
Resolution:
1) Install hotfix 938888.
2) Repair Office 2007.
Sunday, September 20, 2009
How to move the Sharepoint or MOSS site from one server to another quickly using site templates
Create Site template:
http://abc.dca/lmn/_layouts/savetmpl.aspx
Download the stp file from source server
http://abc.dca/_catalogs/wt/Forms/Common.aspx
Upload the stp file to the destination server
http://xyz.dca/_catalogs/wt/Forms/Common.aspx
Create the new site lmn on the destination server using the uploaded custom site template
http://abc.dca/lmn/_layouts/savetmpl.aspx
Download the stp file from source server
http://abc.dca/_catalogs/wt/Forms/Common.aspx
Upload the stp file to the destination server
http://xyz.dca/_catalogs/wt/Forms/Common.aspx
Create the new site lmn on the destination server using the uploaded custom site template
Friday, September 11, 2009
How to use Collect Data from User Activity in SharePoint Designer Workflow
How to use Collect Data from User Activity in SharePoint Designer Workflow
Refn:
http://blogs.msdn.com/bowerm/archive/2007/06/20/sharepoint-designer-workflow-tips.aspx
http://paulgalvin.spaces.live.com/Blog/cns!1CC1EDB3DAA9B8AA!166.entry
While using this Collect Data from User Activity in SharePoint Designer Workflow,
the twist I found was how to get the value entered by the user into workflow local variable
using Set Workflow variable.
Here are the steps:
(1) Click on "value" - "fx"
(2) In Source select Tasks.
Now the lookup will be enabled.
(3) In the field if the one you want to get the value of is not seen, don't worry.
Its because the Collect Data you have created has not been saved.
Go ahead and just use Id for now and then replace it with the actual one later,
or actually create the Collect Data activity by clicking on Finish Workflow button.
(4) In the "Find the List item" section select Task:Id for the Field.
(5) Now for value click on "fx" and
(5.1) Now select the Source as "Workflow Data".
(5.2) and Field as the Collect variable you are storing the "Collect Data" activity into.
Refn:
http://blogs.msdn.com/bowerm/archive/2007/06/20/sharepoint-designer-workflow-tips.aspx
http://paulgalvin.spaces.live.com/Blog/cns!1CC1EDB3DAA9B8AA!166.entry
While using this Collect Data from User Activity in SharePoint Designer Workflow,
the twist I found was how to get the value entered by the user into workflow local variable
using Set Workflow variable.
Here are the steps:
(1) Click on "value" - "fx"
(2) In Source select Tasks.
Now the lookup will be enabled.
(3) In the field if the one you want to get the value of is not seen, don't worry.
Its because the Collect Data you have created has not been saved.
Go ahead and just use Id for now and then replace it with the actual one later,
or actually create the Collect Data activity by clicking on Finish Workflow button.
(4) In the "Find the List item" section select Task:Id for the Field.
(5) Now for value click on "fx" and
(5.1) Now select the Source as "Workflow Data".
(5.2) and Field as the Collect variable you are storing the "Collect Data" activity into.
Subscribe to:
Posts (Atom)
