#community-help

Issue with Colons in Refinement-List Values

TLDR Mr faced an error with colons in values of a refinement-list. Jason suggested a workaround of avoiding colons and making a Github issue for tracking the problem. Mr resolved it with a regex exclusion.

Powered by Struct AI
6
25mo
Solved
Join the chat
Oct 29, 2021 (25 months ago)
Mr
Photo of md5-70864c696bb7a50f63f9b1e057d3c9de
Mr
06:37 PM
Hey Guys , I have a problem, if I have value in refinement-list with colon , I got an error . Tag name datected:DATE_TIME then in request payload send column_tags:=detected:['DATE_TIME'] but it must be column_tags:=['detected:DATE_TIME'] . Thanks in advance!
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
07:34 PM
Could you update to the latest version of the instantsearch adapter to see if that fixes the issue?
Mr
Photo of md5-70864c696bb7a50f63f9b1e057d3c9de
Mr
08:36 PM
Actually , it's in last version
Oct 30, 2021 (25 months ago)
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
03:36 AM
Hmm thought I fixed this… Will take a closer look. Could you open a Github issue so we can track it?
03:37
Jason
03:37 AM
In the meantime, a work around would be to not use colons in the field names, may be use another character instead?
Mr
Photo of md5-70864c696bb7a50f63f9b1e057d3c9de
Mr
03:57 PM
Yeah , I did it in that way, delete colon from text. Actually regex ex. not allow colon from text. I found it yesterday.