{"section":"known-issues","requestedLocale":"en","requestedSlug":"unsupported-fields-by-the-intelligent-search-api-returning-empty","locale":"en","slug":"unsupported-fields-by-the-intelligent-search-api-returning-empty","path":"docs/en/known-issues/Intelligent Search/unsupported-fields-by-the-intelligent-search-api-returning-empty.md","branch":"main","content":"## Summary\n\n\nThe Intelligent Search API is mainly based on the legacy Catalog Search API for compatibility reasons, but not every property returns the same information. In some cases, it is different or empty.\n\nSome affected properties:\n\n- \".items.attachments\" (returns empty)\n- \".items.isKit\" (always return false)\n- \".items.kitItems\" (returns empty)\n- \".items.estimatedDateArrival\" (returns empty)\n- \".items.modalType\" (returns empty)\n- \".items.images.imageText\" (returns the same as \"imageLabel\")\n- \".items.sellers.commertialOffer.PaymentOptions\" (not available, but summarized version available at \".commertialOffer.PaymentOptions\")\n\n\n##\n\n## Simulation\n\n\n\n- register value for an affected field in the Catalog module\n- compare the response for the specific field between the Catalog Search and Intelligent Search APIs\n\n\n##\n\n## Workaround\n\n\nN/A"}