Hi @roser,
Quick question –
What fields are eligible to be returned for direct answers as of 8/20/19?
Are there any field types that are not eligible to be returned?
Thanks,
Liz
Hi @roser,
Quick question –
What fields are eligible to be returned for direct answers as of 8/20/19?
Are there any field types that are not eligible to be returned?
Thanks,
Liz
Hi Liz!
Right now, these are the fields we’re blacklisting from direct answers:
Any field that is type Luhn ( A numeric string with a Luhn checksum), Country Code or Google Place ID
These fields:
location.address_hidden",
"entity.business_id",
"entity.conversation_questions_and_answers_enabled",
"entity.deliver_listings_without_geocode",
"entity.holiday_hours_conversation_enabled",
"entity.entity_id",
"entity.entity_type_id",
"entity.matching_search_ids",
"entity.nudge_conversation_enabled",
"entity.review_response_conversation_enabled",
"location.cluster_index",
"location.is_cluster_primary",
"location.rich_content_suppressed"
I have an item in our backlog that I’ll discuss with engineering tomorrow during our sync on being able to specify blacklisted fields in the config.