Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
Not 100% sure, but I think it is for elasticsearch (which Search & Navigation are built on) knows what property type the field is when searching.
Search should work with no issue
Yeah I was thinking the same thing as some of the fields that START with Search like SearhHitUrl have the $$string on them.
We have some code that sends a Elsatic Search Command through the EpiFind API to JUST update a few extra fields and the $$ doesn't get added. But, I think for now I am going to go with this as is and see if I get the results I am hoping for!
I am using the Epi Search and Nav .Net Client for the first time outside my main Epi project. I have it all setup and working, indexing even.
But, but index documents come out with this $$type postfixes on most fields. What gives? I know those are from serializing, but will they make searches not work?