Goal: Move SharePoint list from old site collection to new site collection.
Approach:
I save the SharePoint list as a template (.stp),
Then move .stp file to the new site collection list template gallery
Create custom SharePoint list using my newly created template
The SharePoint list populates perfectly.
Problem: when I try to edit or add items to the SharePoint list, I’m taken to the default SharePoint page “An unexpected error has occurred”
Open you web.config file of the SharePoint web Application, search for CallStack change it to true and seach for CustomError and set its value to Off. Do the action again you will get to know the actual error causing the error. Rectify it or post the error that will help to point out the issue.
Also notes in case of STP,
If have some LookUp field in the List template, you will need to recreate those fields again or Follow the workaround as described in article
If you have created any Site Column make sure that is there in the new site collection as well.
Related
I have a field in my ssrs dynamics crm report using sql which runs against a case, I need it to display the URL for the sharepoint location for documents related to that case.
Has anyone got any experience and can help on using the correct tables in order to create a expressions which displays the correct URL related for that case for its document location.
sharepointdocumentlocation is the entity which will store document URL in relativeurl attribute. You have to look for case guid in regardingobjectid
Check absoluteurl for fully qualified navigation link. These are totally up to your project for values.
Edit:
From this forum & thread, Its clear that CRM does not have OOB way to store this. Need to write custom code to update a field on record or custom code/query to retrieve absolute URL.
For sharepoint site details, query the sharepointsite entity for absoluteurl or relativeurl.
My object is to create a 2013 reusable workflow that via rest updates a listitem in another list.
(This workflow will be copied via jsom and associated to newly created subsites, so it has to be reusable).
When I try to create variables from "Current item" the site column options are only standard. None of the custom site columns are available.
And there doesnt seem to be a way to use a specific content-type in SP2013 workflow.
Does anyone have a clue?
I ended up doing a differnet approach.
When a user creates a new project (subsite) the list item is created in the main "projectlist" and in the subsite "projectinfo" list.
I made a custom editform to use in the subsites. So when the user edites the item I save it via jsom to subsite projectinfo (where it is edited), then on the callback I update the corresponding listitem in the main project site.
Then i change window.location to the "target" from the query string.
I want to create a web part in which I want to display history of all workflows that failed in the past certain time. The info that I want to get is the workflow name, its location (site URL), initiator and error date time. I am very new to SharePoint with ASP.Net background so I am having a hard time figuring out if there is some way in the API to that?
Kindly share if this is possible?
Its a hidden list so you can't get to it from All Site Content. You have to type the URL in directly, like below. And once you have the URL of the list you can query the individual fields
http://[servername]/[sitename]/lists/Workflow%20History
These days i have faced with very strange problem. I have development environment with MOSS 2007 SP 2 and WS 2008, i have search configured and everything works great. I have started to configuring staging environment (MOSS 2007 SP2 with June CU) and create new farm and new SSP. I have deployed my changes with package (wsp) and manually create site collections, sub webs, pages and so on.
When fill crawl finishes, i see in Crawl log that all my pages have been successfully crawled and when i use some test tools to query search, my pages have been found. In crawl log there is few errors like
http://mysite/sites/de/pages
"The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly..", but all pages in this Page library were indexed.
The problem is that i use custom managed properties (mapped to custom crawled properties) in search queries, but crawler didn't create crawled properties for all my new site columns. For example for site column IsAccent the crawler didn't create cralwed property ows_isAccesnt. I'm sure that i have created pages for specific content type and all my crawl categories have checked "Automatically discover new properties when a crawl takes place ". In site settings -> Searchable columns i haven't got any column selected as Nocrowl.
I tried to export my managed and crawled properties from dev environment to stage evironment but all my managed properties were empty, after that i recreated SSP...the result was the same...
I checked specific page with tools like Sharepoint Manager 2007 and U2U Caml Query Builder 2007 that content type is correct, and i can see values of my custom site collumns.... Using U2U Caml Query Builder 2007 agains some Page library in Result tab i can see ows_IsAccent (my site collumn is IsAccent) and others site columns, but i can't find them in Crawled properties.
Any idias?
Do your lists/libraries that use the new site columns have any items in them?
In order for your Site Columns to show up in the add mapping dialog for metadata properties, you have to have at least one item using that column.
Add an item and then run an incremental crawl.
Look into the definition of the site column, SharePoint tends to create cryptic internal names for the fields promoted to site columns.
You can use something like the Solution Generator (VSeWSS) or the SharePoint Manager 2007 (codeplex) to inspect the site columns and figure out their internal names.
For instance, here is a field promoted to a site column called Internal Description and the xml field definition (from schema.xml) of the form library:
<Field ID="c8607d76_x002d_f648_x002d_47a8_x002d_a189_x002d_8fb8e7e8d18c"
Name="c8607d76_x002d_f648_x002d_47a8_x002d_a189_x002d_8fb8e7e8d18c"
DisplayName="Internal Description"
Required="FALSE"
SourceID="{3FF10E1F-FA95-417c-963D-518F272E2E43}"
StaticName="c8607d76_x002d_f648_x002d_47a8_x002d_a189_x002d_8fb8e7e8d18c"
ReadOnly="TRUE" Group="Microsoft Office InfoPath"
Node="/my:System/my:Internal_Description" Version="1"></Field>
That resulted in the crawled property with the name of:
c8607d76_x002d_f648_x002d_47a8_x002d_a189_x002d_8fb8e7e8d18c
I am trying to connect to simple webparts in my sharepoint team site, i need one of the webparts to filter its information based on what it recieves from another webpart
I am using the query string filter webpart and the a list view webpart but no matter how i connect them always i am getting this error
"Web Part Error: This page has exceeded its data fetch limit for connected Web Parts. Try disconnecting one or more Web Parts to correct the problem."
What should I do and what am I doing wrong
update:
i can connect to web parts on some other pgae, but getting this error on the DispForm.aspx page of a certain item , is webpart connections not allowed there ??!!
There is an issue with creating QueryString filter webparts in sharepoint, when you're not using the Web UI (I'm making an assumption that you aren't).
This fella here has a post about it and how he hacked around the issue.
http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/0328f1b2-20cd-427f-887a-e2925bd695e3/
Another option is not using the QueryString filter web part at all, and just passing querystrings to a regular web part.
http://mo.notono.us/2008/04/moss-filter-views-through-url-query.html
Me too,you look this url
http://blogs.msdn.com/sharepointdesigner/archive/2008/03/26/sharepoint-conference-building-a-sharepoint-designer-mashup-part-1.aspx
I have fixed this issue.
Problem
In the sharepoint list, filtered column name in query strng fitlter has been deleted and added new column with same name.
Solution: Remove filter and Set current view again in webpart properties. It works fine.
With Regards,
Marees
The page 'DispForm.aspx' usually is a form of a SharePoint list and different rules apply to list-form pages than on pages that do not belong to a Sharepoint list (and the differences are hardly documented). I solved the problem by workarounds; you could use not a ListViewWebPart, but a DataViewWebPart (Using Query String and Data view WebPart), or you could avoid the QueryStringFilterWebPart by using URL parameters that the ListViewWebPart understands (ListViewWebPart Filter Param).