A client of mine has 2 web applications, sharing the same content types.
These content types (let's call them "A") are of a base type DocumentSet, and include a Managed Metadata Property "B" (which is a indexed column on WebApp 2 in all libraries).
There's one strange thing going on however. Searching and indexing works fine. But when we search in WebApp 2, it always shows the value of the Managed Metadata Property field "B" in the description. And it's always the wrong one. Whatever the real value is of property B in that documentset, it always shows a certain other value from the taxonomy store.
I tried inspecting every single property and field of the item in Powershell, but could not find any reference to the displayed property value.
My question in this matter is:
1) How on earth could this value be crawled and included in the description if it does not exist in the list item?
2) How can I inspect the crawl database to check what properties it has stored?
Related
I have created one content part say News which is attachable, having one property of type DateTime
I have attached this content part to one content type.
in content type I have set "Include in index" for my DateTime field of content part.
now i have created one index say NewsIndex.
Set this newsIndex in content type (Published Version)
Rebuild index.
now when i go to Settings->Search, I am not able to see my DateTime field check box over there.
I am using Orchard version : 1.10.1.0
I have tried above situation by both way.. (From admin dashboard and using Code)
Facing this issue since 5 day, trying a lot but not able to get success. Really needed help on this.
For example, if my page contains the following code:
<a id="foo" href="#">Click Me!</a>
Is there a way with CodedUI to verify that a link with id equal to "foo" is present on the webpage?
Inspect the link with the Coded IU cross-hairs (ie assertion building) tool. The properties shown should include the Id field. You can then generate an assertion that the link contains the text Click Me!. Make sure the generated search properties include the required value for the link property. If the Id field or the displayed text are variable (perhaps their values are data driven or found earlier in the test) then before finding the control (implicitly or explicitly) set the required values. This should work because the assertion can only be checked if the required field is found on the screen and that find uses teh Id field.
Perhaps your question is a more general "is there such a link anywhere on the web page"? If so then you can use the GetChilden() to do a recursive traverse of the web page. Check each UI Control found to see if it has the desired values.
I am trying to create a Page Layout, that should have a lookup field. Lookup field should always get populated with a list's items.
This list will exist in all subsites, so whereever I create this page, list should get populated with listitems from current site.
I tried using site column lookup field, but it always point to list under top site and not the current site.
Any suggestion on how to make it work or better alternative? Thanks!
Let me know if I can provide more info.
The most straightforward solution I can think of is using a cross site lookup column and creating a seperate fields for each subsite. However, you will need to create and use different Page Layouts for each subsite.
You can use http://sp2010filteredlookup.codeplex.com/ for cross site lookups.
Solution 1 - Use http://sp2010filteredlookup.codeplex.com/
Use filtered lookup solution. So let's say you have your custom Page Layout and custom Page Content Type.
Every time you create new subsite, you should remember go to Pages list settings and edit Page Content Type by adding cross site lookup (with the same field "internal name").
So you still have one Page Layout (and one Content Type). But for each Pages library instance, Content Type contains diff fields (but with the same Internal Name). It will allow you run CAML queries and other things needed without any problems.
Solution 2 - develop custom sharepoint field type.
In edit mode, control will render "dropdown list" and populate data from list instance that is on current subsite. In the field settings you can have relative list url.
Solution 3 - hidden text field / js snippet solution
Page Content Type can contain hidden text field (it can contains selected field value in json format for example). Develop js snippet that will handle all the logic (rendering in edit/view mode, saving etc) and put it on Page Layout (aspx).
I would suggest to use solution #1 or #2.
I've made a custom content type based on the "Page publishing".
In this content type, I've also made a lookup field that lists all items in a list (nothing special with that list though)
When I use my own user to look at a page made with my custom content type, no problem.
When the site is crawled, the crawler doesn't want to index it giving me the error :
“ Content for this URL is excluded by the server because a no-index attribute.”
So I logged in with the same user as the crawler, and when I try to see the page, I get this error :
The page you selected contains a list that does not exist. It may have been deleted by another user.
Still, with that user, I can see the list that is used in the lookup field without any problem...
Any idea?
Moved to Server Fault:
Sharepoint managed Properties
I have a custom Content Type inside a list that has over 30 items, and I have added several "managed properties" to the "crawled properties", in the SSP.
All of them work except 1.
The column "Synopsis" is a multiline field with no limit on it's length. It appears as a crawled property "Synopsis", and is mapped to a managed property 'asynop'.
On the 'Advanced Search Page', it is added as a property and searchable, however it only returns a partial result (if at all). I manually created an entry, ran the crawl and was able to search for it. I edited an existing entry, ran the crawl (full and incremental), and it still only returned the manually entered entry.
If I entered the search term in the Search box directly "synopsis:fatigue", then all the correct results appear.
What the is happening? And could it please stop?
This is a known issue and is dependent on what type of search is executed.
See Steve Currans great answer to this post: http://social.technet.microsoft.com/Forums/nl/sharepointsearch/thread/f3f1d778-796e-4321-9c76-a6ede421a42f