I have a problem with the Elastic indexation of the documents.
Many documents are not retrieved on research (on portlets and on administrations pages).
When I do the reindex by Administration page, I see on logs missing documents.
If I modify the document manualy, the document is retrieve on research.
What is the problem ?
Samuel
(Sorry for my bad english ;) )
The problem is due to incoherences on DB.
Table ddm_content was not correctly set (data_ column).
Best regards
Related
I know there are threads out there about making changes to the refinement panel and they have so far been very helpful but now I have a question that I need a bit more assistance with.
I've created a new filter for the refinement panel. That worked very fine.
I can see the filter, when I perform a search.
But when I click on the new filter, all search results disappear and it just says: "We did not find any results for ".
I can see that the url gets my created filter attached:
results.aspx?...&r=filterfield%3D%22True%22
I have created a managed metadata property and added the field to the search results (search core results webpart).
What I'm doing wrong? Why it doesn't work?
Any hints?
Thanks for any help.
I found the reason. I forgot to start a full crawl after creating the managed metadata field.
Is there a way to have user selected records remain selected as the pages are changed in the view? Currently, when changing pages in the view, the selection is lost.
For example, the user is looking at the Accounts entity, and wishes to select a few records from the first page of results and other records from subsequent pages.
I have explained that this is standard behaviour and that they should further filter their results but they are insisting that I try to find a solution.
There isn't a supported solution to your problem other than writing custom web-resource pages that will do exactly what you need.
I'm sure you've already told them to set their "records per page" to 250 in their Preferences.
In CRM 4.0, I once figured out where this "records per page" setting is stored in the database and I was able to change it to 5000 directly in the database. It did work (I think I had to iisreset as well), but it is obviously unsupported and could cause massive performance issues.
I am about to use Solr'd Dynamic Fields for the first time but my requirements state that those fields have to be facetable. I did quite a lot of googling and doc reading but I can't find a place that either confirms or denies the allegation :)
Does anyone here know?
Thanks in advance!
Andre
Yes, you can facet on dynamic fields just fine.
Dear StackOverflow members,
I'm currently facing an issue with one of my SharePoint server, the contentclass assigned to the crawled content is never set.
I noticed that when my scopes returned 0 result (I'm filtering on contentclass=sts_list_item_850). A quick search with the neat ZevenSea SearchCoder within the crawled content confirmed this
(no content class is available, field is empty accross all crawled content).
I deleted my scopes, did a full crawl, even deleted my SSP and create a new one, running the configuration wizard but this behavior is still here and I've no clue why it's the case.
If you have any idea what could be the culprit, I'm eager to know.
Thanks a lot for any feedback.
I also had the same issue and I noticed that in the search schema the mappings of the managed property were not complete. I added all the mappings in the correct order and the issue has gone (I copied mapping and order from a farm where it was working well).
I have a cakePHP application with an advanded search section. When a user applys filters, they are lost when they navigate to an indivual record and then return to search page.
How / What is the best way to keep "memory" of this information and re apply it on page load?
Thanks Paul
Storing parameters in the session has some disadvantages when talking about storing searching criteria.
For example, using sessions is a good way for storing a shopping cart data or logged in user, because this state is the same when you open another new tab too.
But imagine when you apply some search filter, open a new tab with the same page, and then you see the same criteria you filled in previously opened page.
Try storing the search parameters in the session. Note that this isn't something that CakePHP can bake for you. You'll need to implement this yourself.
In case this is helpful: I extensively use this Filter plugin for my searches/filtering:
https://github.com/lecterror/cakephp-filter-plugin
This plugin actually stores the search query across a session, so might be worth having a look at how it does it. In addition to storing a query - it also saves the filter query for each specific model without affecting the others.