Hi,
Just found this, does JsonIgnore really ignores the properties when the episerver find is running its indexing job? How effective will this attribute be?
Regards,
Ram
1. I use the index browser support in find gui on site to explore what has been indexed or not. That is usually the first troubleshooting step. See
http://world.episerver.com/blogs/Mari-Jorgensen/Dates/2013/2/Hidden-Gems-of-EPiServer-Find/
for example
2.
I use conventions to determine what objects and fields to index to keep it separate. Jsonignore attribute works too but I prefer to keep that logic separate.
http://world.episerver.com/documentation/Items/Developers-Guide/EPiServer-Find/10/Integration/EPiServer-75/Indexing/
Example:
Hi Mark,
Thanks for your reply.
[JsonIgnore] attribute has helped a bit. I would like to get logs from EpiFind to learn more about what is happening.
Thanks,
R
Hi Episerver Support,
How do I add myself as a developer to use your support form. We hold two EpiFind license, I guess that make me be able to use the support forum?
Regards,
Ram
Hi All,
The Episerver Indexing Job is producing inconsistent results in our staging site.
Our site is content heavy with close to 70000 content types. Since the product and the variant indexing is now messed up there is no products displayed in the site.
I have the below questions that needs answers. I appreciate your time on this.
1) Can we get our log files from the episerver find cloud to understand what is causing this issue? (Basicaly we would like to know if our indexing job send the correct findin to find cloud).
2) Is there a way I can mark a property/fields to be ignored when episerver find does its indexing job? (something like [Ignore] on top of the property defenition, see below)
Any insights are very much appreciated.
Regards,
Ram