Home Original page

feat(context-grounding): expose index_id on UnifiedQueryResult by cfauchere · Pull Request #1534 · UiPath/uipath-python

@claude 

unified_search and unified_search_async already resolve the index by
name to get its ID for the API call, but discard it before returning.
This adds index_id to UnifiedQueryResult and sets it from the resolved
index, so callers can include it in trace spans for debugging.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

cfauchere pushed a commit to UiPath/uipath-langchain-python that referenced this pull request

Mar 31, 2026 
Depends on UiPath/uipath-python#1534 which exposes index_id on the result.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

cfauchere pushed a commit to UiPath/uipath-langchain-python that referenced this pull request

Apr 1, 2026

Clement Fauchere and others added 4 commits

March 31, 2026 20:22
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Extend index_id to all CG operations, not just unified_search:
- start_deep_rag / start_deep_rag_async
- start_batch_transform / start_batch_transform_async
- start_deep_rag_ephemeral / start_deep_rag_ephemeral_async
- start_batch_transform_ephemeral / start_batch_transform_ephemeral_async

Added index_id field to BatchTransformCreationResponse and
DeepRagCreationResponse models.

Every CG operation that resolves or receives an index_id now returns it
on the response, so traces can include it for debugging.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>