#community-help

Resolving Error with Schema Config in FE

TLDR KARTHICK faced an error with the schema config, while Jason clarified the need for string fields in query_by, resolving the issue.

Powered by Struct AI
3
4mo
Solved
Join the chat
May 27, 2023 (4 months ago)
KARTHICK
Photo of md5-9885c2d5db3a85d24bc9c11809bcaf50
KARTHICK
08:56 AM
I already have schema config for isQuickApply and isExternalApply as bool.But its throwing this error in the FE. Jason Kishore Nallan
Image 1 for I already have schema config for isQuickApply and isExternalApply as bool.But its throwing this error in the FE. <span class="s-mention s-user"> <strong>Jason</strong></span> <span class="s-mention s-user"> <strong>Kishore Nallan</strong></span>Image 2 for I already have schema config for isQuickApply and isExternalApply as bool.But its throwing this error in the FE. <span class="s-mention s-user"> <strong>Jason</strong></span> <span class="s-mention s-user"> <strong>Kishore Nallan</strong></span>
May 28, 2023 (4 months ago)
Jason
Photo of md5-8813087cccc512313602b6d9f9ece19f
Jason
02:40 AM
It sounds like you’ve added boolean fields to query_by. You only need to add string / string[] fields to query_by
May 29, 2023 (4 months ago)
KARTHICK
Photo of md5-9885c2d5db3a85d24bc9c11809bcaf50
KARTHICK
04:27 AM
ohhh got it.I thought the schema should be same as we have in the primary db.I didnt notice that.