Community Contribution Intake — Triage #1 (2026-03-13)

[saurabhrb]

Community Contribution Intake -- Triage No. 1 (2026-03-13)

Triage Window: All open PRs and issues as of 2026-03-13T23:59:59Z
Next Triage: Triage No. 2 -- first week of April 2026 (covers activity after 2026-03-13T23:59:59Z)
Triaged by: @saurabhrb
Current SDK version: v0.1.0b6
Total PRs reviewed: 16 | Total Issues reviewed: 2

Thank you to everyone who has contributed to the PowerPlatform Dataverse Python SDK. We genuinely appreciate the time, expertise, and thoughtfulness that each contributor brings to this project. This triage captures a snapshot of all open contributions so the team can prioritize, coordinate, and ensure every contribution receives a clear response.

Note: This SDK is in early public beta (v0.1.0b6). The team is actively working on foundational design and implementation. All version targets and timelines in this document are aspirational estimates provided for transparency and planning purposes only. They are subject to change based on internal review, design decisions, testing outcomes, and shifting priorities. We share them so the community has visibility into our thinking -- not as commitments. We will update this triage (or subsequent ones) if plans change materially.

Response goal: We aim to acknowledge every community PR and issue within 15 business days. As the SDK is in early beta with a small team, response times may occasionally vary. If you haven't heard from us, please feel free to ping this issue -- we want to make sure nothing is overlooked.

---

Internal Development Status

The following PRs and issues are actively being developed by the Microsoft SDK team. Where internal work overlaps with or addresses a community contribution, we've cross-referenced the relevant community PR/issue so contributors can track progress.

PR/Issue	Title	Owner	Status	Target Version*	Community Cross-Reference
PR #98	Add dataframe methods	@zhaodongwang-msft	In progress	v0.1.0b7*	--
PR #11	Add CreateInstantEntities API	@zhaodongwang-msft	In progress	v0.1.0b7*	--
PR #129	Implement batch API including with changeset	@sagebree	In progress	v0.1.0b7*	--
PR #118	Add QueryBuilder with fluent API	@tpellissier-msft	In progress	v0.1.0b7*	--
PR #119	Add telemetry hooks with OpenTelemetry	@tpellissier-msft	In progress	v0.1.0b7*	--
PR #50	Retry logic improvements + fix warnings	@suyask-msft	In progress	v0.1.0b7*	--
PR #136	Add async/await support (AsyncDataverseClient)	copilot-swe-agent	In progress	v0.1.0b8*	--
PR #141	Add public schema discovery APIs	copilot-swe-agent	In progress	v0.1.0b7*	Addresses community PR #132 (@maksii)
PR #135	Add opt-in HTTP diagnostics logging	copilot-swe-agent	Under evaluation	TBD	Related to internal PR #119
PR #133	[DRAFT] Feature/capture telemetry	@saurabhrb	Draft	TBD	Related to internal PR #119
PR #134	[WIP] Add async/await capability	copilot-swe-agent	To be closed	--	Superseded by PR #136
PR #41	Delete update (delete_async + elastic table)	@zhaodongwang-msft	Deferred	v0.1.0b8*	To be folded into PR #136

* Target versions are aspirational estimates, not commitments. See disclaimer below.

---

Community Contributions -- Pull Requests

We value every pull request from our community. Below, we've organized contributions by priority to provide transparency on how we plan to incorporate them. If your contribution is listed under "Future Consideration," it does not mean it's unimportant -- it means we want to sequence it thoughtfully alongside our internal roadmap.

Required

Contributions the team considers essential for upcoming releases.

#	PR	Title	Author	Opened	Status	Action	Target*
1.1	#131	Add FetchXML query support to Dataverse client	@maksii	2026-02-28	Open	Review -- self-contained feature with tests and documentation. Thank you, @maksii, for the thorough implementation including paging and validation.	v0.1.0b7*
1.2	#83	Cache empty result for picklist label retrieval	@pkontek	2025-12-18	Open	Review -- small, focused performance fix. Thank you, @pkontek, for identifying this optimization.	v0.1.0b7*

Good to Have

Valuable contributions that improve the SDK but are not blocking the next release.

#	PR	Title	Author	Opened	Status	Action	Target*
2.1	#132	Add extended table metadata retrieval and models for columns and option sets	@maksii	2026-02-28	Open	Under review -- overlaps with internal PR #141. We appreciate the typed model approach, @maksii, and will evaluate how best to incorporate this with our internal metadata work.	v0.1.0b7*
2.2	#78	Add file download and file delete operations	@pkontek	2025-12-10	Stale (90+ days)	Rebase needed -- extends client.files with download and delete. Thank you, @pkontek. This PR has been inactive for 3+ months -- we'd welcome an updated version rebased against main.	v0.1.0b8*

Future Consideration

Contributions that align with the long-term roadmap but are not currently prioritized.

#	PR	Title	Author	Opened	Status	Action	Target*
3.1	#12	Add ability to create relationships in initial table definition or as separate operation	@jeffandms	2025-09-17	Stale (90+ days)	Rebase needed -- expands table creation schema and adds relationship methods. Thank you for the early contribution, @jeffandms. This is 6 months old -- we'd appreciate a rebase so we can evaluate compatibility with current main.	TBD

Addressed / Duplicates

Community contributions already covered by internal work, or duplicates of other items. When a community PR is addressed, we note the commit SHA and/or release version here for traceability.

No items in this triage.

---

Community Contributions -- Issues

We appreciate every issue filed by the community. Bug reports and feature requests help us build a better SDK for everyone.

Required

#	Issue	Title	Author	Opened	Status	Action	Target*
I-1.1	#77	@odata.bind problem with same column and table names	@JakubStarobrat	2025-12-09	Open	Investigate -- OData binding fails when a lookup column's logical name matches another table's name. Thank you for the detailed reproduction steps, @JakubStarobrat. We're evaluating whether the SDK can provide a workaround or if this should be documented as a Dataverse platform behavior.	v0.1.0b7*

Good to Have

#	Issue	Title	Author	Opened	Status	Action	Target*
I-2.1	#76	Better data type specification	@MarcusRisanger	2025-12-04	Open	Acknowledged -- valid feedback that column creation lacks control over constraints (string max length, numeric ranges). Thank you, @MarcusRisanger, for the thoughtful comparison with your own library. We plan to address this as part of our metadata/schema enhancement work (internal PR #141).	v0.1.0b7*

Addressed / Duplicates

No items in this triage.

---

Release Roadmap

A brief summary of upcoming releases and which community contributions are being considered for each.

Version	Estimated Timeline*	Community PRs	Community Issues	Notes
v0.1.0b7*	Q2 2026*	#131 (FetchXML), #83 (cache fix), #132 (metadata models)	#77 (OData bind), #76 (data type specs)	Next beta -- query enhancements, metadata discovery, performance, telemetry
v0.1.0b8*	Q3 2026*	#78 (file download/delete)	--	Async client, file operations expansion
v1.0.0*	TBD	#12 (relationships)	--	GA release -- remaining roadmap items, stability, API finalization

---

Disclaimer:* All target versions*, estimated timelines*, and release plans in this document are provided for transparency and planning purposes only. They represent the team's current thinking and are not commitments. Targets are subject to change based on internal design reviews, testing outcomes, resource availability, dependency changes, and evolving priorities. We will communicate material changes in subsequent triage issues. We appreciate the community's understanding as we work to build a stable, high-quality SDK.

---

Action Items

Internal

• Close PR [WIP] Add async/await capability to Dataverse Python SDK #134 -- superseded by Add async/await support via parallel AsyncDataverseClient hierarchy #136
• Finalize PR Add async/await support via parallel AsyncDataverseClient hierarchy #136 (async client) -- fold PR Users/zhaodongwang/delete update #41 delete changes
• Consolidate telemetry approach -- PR Add client-side telemetry hooks with OpenTelemetry integration #119 as primary, evaluate Add opt-in HTTP diagnostics logging with automatic header redaction #135 as hook, clarify Add client-side telemetry hooks with OpenTelemetry integration and ad-hoc capture #133
• Consolidate metadata approach -- align PR End-to-end SQL support: schema discovery, SELECT * expansion, DataFrame bridge, helpers, guardrails #141 with community PR Add extended table metadata retrieval and models for columns and option sets #132

Community PRs

• Review PR Add FetchXML query support to Dataverse client #131 (FetchXML by @maksii) -- target v0.1.0b7
• Review PR cache empty result for picklist label retrieval in _ODataClient #83 (cache fix by @pkontek) -- target v0.1.0b7
• Review PR Add extended table metadata retrieval and models for columns and option sets #132 (metadata models by @maksii) -- coordinate with internal PR End-to-end SQL support: schema discovery, SELECT * expansion, DataFrame bridge, helpers, guardrails #141, target v0.1.0b7

Community Issues

• Investigate issue @odata.bind problem with same column and table names #77 (@JakubStarobrat) -- target v0.1.0b7
• Acknowledge issue Better data type specification #76 (@MarcusRisanger) -- link to metadata/schema roadmap, target v0.1.0b7

---

Stale Contributions

The following contributions have had no activity for 90+ days and are at risk of closure per our stale policy. We will post a courteous comment on each, asking the contributor if they plan to continue. If no response within 30 days, we will close with an invitation to reopen.

PR/Issue	Title	Author	Last Activity	Days Inactive
PR #78	Add file download and file delete operations	@pkontek	2025-12-10	~93 days
PR #12	Create relationships in table definition or separately	@jeffandms	2025-09-17	~178 days

---

Process Notes

This is the first Community Contribution Intake triage. Future triages should:

1. Title: Community Contribution Intake -- Triage No. N (YYYY-MM-DD)
2. Labels: triage, internal-tracking
3. Cadence: Monthly -- first week of each month
4. Cutoff: Cover only PRs/issues opened or updated after 2026-03-13T23:59:59Z
5. Reference: Link to this issue ("Continues from Community Contribution Intake — Triage #1 (2026-03-13) #144")
6. SDK version: Check version in pyproject.toml on main -- that shows the next release version; current public release is one version lower
7. Internal devs: saurabhrb, maxwang96, sagebree, suyask-msft, tpellissier-msft, zhaodongwang-msft -- list their PRs/issues in the Internal Development Status section
8. Cross-reference: When internal work addresses a community contribution, note the community PR/issue number explicitly
9. Target versions: Every community PR/issue must have a target release version or TBD
10. Carry forward: Any unresolved action items from this triage
11. Stale policy: Flag contributions with 90+ days of inactivity; close after 30 more days without response
12. Notification comments: After publishing the triage, post a comment on each triaged community PR/issue with the outcome
13. Addressed items: When a community contribution is merged, record the commit SHA and release version in the Addressed / Duplicates tier
14. Categories: Required, Good to Have, Future Consideration, Addressed/Duplicates