fix: Added advanced field option and offset support#814
Conversation
AditiGoyalUipath
commented
May 18, 2026
AditiGoyalUipath
commented
- Skills update to support advanced option in field like field length,max min value
- Offset support in get API.
AditiGoyalUipath
force-pushed
the
fix/advancedField
branch
2 times, most recently
from
2d30de9 to
e26e65a
Compare
There was a problem hiding this comment.
Pull request overview
This PR updates the UiPath Data Fabric skill’s documentation and coder-eval task definitions to cover (1) advanced per-field constraints in entity schema operations and (2) offset-based pagination support alongside cursor pagination for records list/query.
Changes:
- Expanded Data Fabric smoke/integration tasks to exercise advanced entity field constraints (lengthLimit, minValue/maxValue, decimalPrecision) and to require offset pagination usage.
- Added/updated success criteria patterns to detect cursor pagination, offset jumps, and forbidden pagination-in-body usage.
- Updated skill documentation and reference docs to describe advanced field constraints and
--offsetpagination.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| tests/tasks/uipath-data-fabric/smoke_records.yaml | Updates the offline smoke task prompt + success criteria to require --offset and enforce pagination rules. |
| tests/tasks/uipath-data-fabric/smoke_entities.yaml | Expands the offline entities smoke task to include advanced field constraint usage and checks. |
| tests/tasks/uipath-data-fabric/integration_large_pagination.yaml | Extends the large pagination integration task to validate offset-page jumps vs cursor-walked IDs. |
| tests/tasks/uipath-data-fabric/integration_full_lifecycle.yaml | Adds advanced field constraint creation/verification/tightening to the full lifecycle integration task. |
| skills/uipath-data-fabric/SKILL.md | Adds sections documenting advanced field constraints and pagination (--offset). |
| skills/uipath-data-fabric/references/records-query.md | Documents --offset semantics and mutual exclusivity with --cursor. |
| skills/uipath-data-fabric/references/entity-schema.md | Documents advanced per-type field constraints and how they appear in entities get. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
AditiGoyalUipath
force-pushed
the
fix/advancedField
branch
from
e26e65a to
3985649
Compare
| - type: command_executed | ||
| description: "Agent must NOT combine --offset and --cursor on the same command" | ||
| tool_name: "Bash" | ||
| command_pattern: 'uip\s+df\s+records\s+(list|query)(?=[^\n]*--cursor)(?=[^\n]*(-o\s+\d+|--offset\s+\d+))' | ||
| min_count: 0 |
| - type: command_executed | ||
| description: "Agent must NOT put pagination keys inside the --body JSON" | ||
| tool_name: "Bash" | ||
| command_pattern: '(?s)uip\s+df\s+records\s+query.*--body.*\"(start|offset|pageSize|limit)\"\s*:' | ||
| min_count: 0 | ||
| max_count: 0 |
SuphalAthlur
left a comment
SuphalAthlur
left a comment
There was a problem hiding this comment.
And do we have these guardrails enforced in the CLI command? Things like is the constraint applied permitted for the chosen field type etc.
| > `start` and `limit` are **not** valid body keys — use `--limit` and `--cursor` CLI flags instead. | ||
| > `start`, `limit`, `offset`, and `pageSize` are **not** valid body keys — use `--limit`, `--cursor`, and `--offset` CLI flags instead. The CLI translates them into the underlying offset-based API call. |
There was a problem hiding this comment.
Wondering if the first part is a necessary clarification
There was a problem hiding this comment.
Can you clarify this ?
There was a problem hiding this comment.
As in, can't we have something like this? Why do we need to mention properties that are invalid, we could directly provide the valid flags right?
use
--limit,--cursor, and--offsetCLI flags ONLY. The CLI translates them into the underlying offset-based API call.
| ``` | ||
|
|
||
| Pagination for query also uses `--limit` and `--cursor` flags — not body keys. | ||
| Pagination for query also uses `--limit`, `--cursor`, and `--offset` flags — not body keys. |
There was a problem hiding this comment.
Is --cursor used for querying VDO entities alone?
There was a problem hiding this comment.
No this is supported in SDK for cursor based pagination. User can use limit based(Which is supported in datafabric API) or cursor based pagination (supported via sdk)
Guardrails are enforced in typescript SDK which CLI invokes to perform any action. |
…thored-By: Claude Opus 4.7 <noreply@anthropic.com>
AditiGoyalUipath
force-pushed
the
fix/advancedField
branch
from
3985649 to
edf03dc
Compare
