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
Related
I have videos embedded as links in Sharepoint , these videos are not part of SharePoint farm. I need to search for these URLs and replace with different URLs. Is there any search configuration that am missing.
I have an approach but it's a little bit tricky:
What you could do is to create a new Text managed property that maps to the A.HREF crawled property which is the href of a hyperlink. You'll have to enable the Queryable and Retrieveable settings for it (Remember to perform a FULL CRAWL after you've created a new managed property).
After the managed property is created you could perform a search using your new property in the search condition.
I have a requirement to display SharePoint Documents Sub Grid on the MS crm Dynamics 365 Custom Entity Form.
Can anyone let me know, how to achieve this using Supported or unsupported way?
You can find solution here:
You may use the below line of code to set the Iframe url to display the subgrid in iframe:
Xrm.Page.getControl("IFRAME_Documents").setSrc(Xrm.Page.context.getClientUrl() + "/userdefined/areas.aspx?formid=" + CurrentFormId + "&inlineEdit=1&navItemName=Documents&oId=%7b" + recordId + "%7d&oType=" + oTypeCode + "&pagemode=iframe&rof=true&security=852023&tabSet=areaSPDocuments&theme=Outlook15White");
Where:
“IFRAME_Documents” is the Iframe name.
“CurrentFormId”= Is the Current selected form id which you can get using Xrm.Page.ui.formSelector.getCurrentItem().getId().replace("{", "").replace("}", "");
“recordId” = Record’s GUID
“oTypeCode” = Entity Type Code which you can get using Xrm.Page.context.getQueryStringParameters().etc;
This is how I did in D365. (Using Chrome made it easier)
Enable document management for the entity
When Documents tab shows
for the entity record open it.
Then open Chrome dev console (F12)
Grab the panel (which is actually an iframe) source. The URL is of format:
/userdefined/areas.aspx?appid=...........&formid=.......&inlineEdit=1&navItemName=Documents&oId=.....&oType=.....&pagemode=iframe&rof=true&security=......&tabSet=areaSPDocuments&theme=Outlook15White
Replace the dotted values in the source URL with appropriate values
and make the URL fully qualified prefixing with the root.
Just ensure not using any hardcoded GUIDs or IDs in the values. In this way this can be reused easily wherever needed.
Latest: Recent version has direct OOB customization to achieve this.
Dynamics 365: Related Documents Now Display on Record’s Main Form
Add or remove the SharePoint documents tab to the main form for any table
In short: Server to Server integration approach shows physical documents in crm grid. No need of iframe solution.
Old school List component integration has a limitation, it shows document location crm records in crm grid, so you need iframe solution to show physical docs from Sharepoint.
[Applicable to Server based Integration] - It will show Documents in the grid.
Open an Entity Web form where you want to display SharePoint document library.
Click on the Insert-tab, click on Sub-Grid, specify a name to sub-grid
In “Data Source” section select “Only related Records” from Records dropdown
Select “Document Location (Regarding)” in Entity dropdown
Select “Active Document Location” from Default View section [shown in Below Image]
Click on Set. Click on save then publish the customization
Reference
Update: [Applicable to List component Integration]
Associated view will show what we want but subgrid is not working as expected. Upon research, this is product limitation. Read more
sometimes it is desirable to have an “at a glance” view of documents associated with a record. In order to view the documents in SharePoint that are related to a record, the user must navigate to a related entities area outside of the form. (Similar to Connection, or other related entities)
For most related entities, a sub-grid can be used in the form to display the relationships immediately on the form, but there is no simple workaround for the Documents.
Another alternative is showing Associated view in IFRAME.
EDIT:
In latest Dynamics 365, CRM + Sharepoint integration using List component is deprecated. Only way is Server to Server (S2S) based CRM + Sharepoint integration is possible. This S2S approach shows documents in the associated grid & subgrid, not the doc location like in List component. CRM - Sharepoint wrapper taking care of conversion from CRM FetchXML to SP CAML query & give us the result we want.
The great thing about having the documents queried by CRM is that you
can create custom views of documents in the same way you would with
any other entity in CRM. When using the list component the default
view in SharePoint was rendered in the IFRAME meaning that to get new
columns you had to have list customisation privileges on SharePoint
such that all users would see the changes. With the new server to
server integration you can select SharePoint columns to include in
your own views and even add in your own filters using the CRM advance
find interface.
Read more.
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
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.
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).