@mohsinonxrm/pptb-dataverse-request-studio 1.0.0 → 1.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +75 -0
- package/dist/assets/index-Dbsyt-Z9.js +672 -0
- package/dist/index.html +1 -1
- package/npm-shrinkwrap.json +2 -2
- package/package.json +96 -96
- package/dist/assets/index-5a71OtQP.js +0 -672
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,81 @@ All notable changes to Dataverse Request Studio will be documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
|
|
8
|
+
## [1.1.1] - 2026-06-08
|
|
9
|
+
|
|
10
|
+
### 🐛 Fixed
|
|
11
|
+
|
|
12
|
+
- **Custom OptionSet (and other typed) values incorrectly quoted as strings in
|
|
13
|
+
`$filter` over a lookup navigation** ([#33](https://github.com/mohsinonxrm/pptb-mxrm-dataverse-request-studio/issues/33)).
|
|
14
|
+
Filtering on a related-entity column via a nav path — e.g.
|
|
15
|
+
`msdyn_opportunityid/abc_salesstage eq 809770000` — emitted the value as a
|
|
16
|
+
quoted `Edm.String` (`'809770000'`), which Dataverse rejects with HTTP 500
|
|
17
|
+
/ `0x80060888`. Standard columns appeared to work only by coincidence (the
|
|
18
|
+
root entity happened to own a same-named column). Root cause: the `$filter`
|
|
19
|
+
encoder resolved the leaf column against the **root** table instead of
|
|
20
|
+
walking the relationship to the **related** entity, so the leaf's
|
|
21
|
+
`AttributeType` never drove the quoting decision. The encoder now resolves
|
|
22
|
+
nav-path leaves against the correct related entity, so numeric/boolean/choice
|
|
23
|
+
types are emitted unquoted and strings/GUIDs are quoted, consistently.
|
|
24
|
+
|
|
25
|
+
### ✨ Added / Changed (architecture)
|
|
26
|
+
|
|
27
|
+
- **Single, metadata-driven nav-path resolver (`resolveNavPath`)** in
|
|
28
|
+
`mock/metadata.ts` — now the one source of truth for resolving a
|
|
29
|
+
slash-delimited path (`nav/.../leaf`, alias-aware) to its leaf `ColumnMeta`,
|
|
30
|
+
owner table, visited chain, and first not-yet-loaded hop. The `$filter`
|
|
31
|
+
encoder (`colLookup`), the filter editor's leaf/pending-target resolution,
|
|
32
|
+
and the `$orderby` warnings all route through it, eliminating duplicated
|
|
33
|
+
walk logic that had drifted out of sync.
|
|
34
|
+
- **Related-entity metadata pre-warming (`useWarmReferencedTables`)** — the
|
|
35
|
+
Retrieve Multiple / Retrieve Single modes now walk the `$filter`, `$expand`,
|
|
36
|
+
`$apply`, and `$orderby` trees and pre-fetch the related entities they
|
|
37
|
+
reference. This makes correct type resolution independent of whether the
|
|
38
|
+
user opened the relevant editor — covering **saved-request reload**,
|
|
39
|
+
**pasted OData URLs**, and **direct Execute**. Targeted (only referenced
|
|
40
|
+
entities) and self-healing across multi-hop paths, so it stays clear of the
|
|
41
|
+
100-concurrent-request cap.
|
|
42
|
+
- **Paste-OData parsing** now validates and pre-loads nav-path filter leaves
|
|
43
|
+
instead of skipping them.
|
|
44
|
+
- **Metadata cache TTL raised from 5 minutes to 1 hour**, with a new
|
|
45
|
+
**Settings → Refresh metadata** button (`metadata.refreshAll`) to force a
|
|
46
|
+
fresh pull after publishing schema changes mid-session.
|
|
47
|
+
|
|
48
|
+
## [1.1.0] - 2026-05-25
|
|
49
|
+
|
|
50
|
+
### ✨ Added
|
|
51
|
+
|
|
52
|
+
- **Scope-setup guidance banner** — when the tool loads with the entity scope
|
|
53
|
+
unconfigured (i.e. `entityScopeMode` is `publisher-solution` or
|
|
54
|
+
`solution-only` but no solutions have been selected), a contextual
|
|
55
|
+
`MessageBar` (warning intent) is shown at the top of the Target pane across
|
|
56
|
+
**all 14 modes** that use `TargetEditor`. The banner provides a mode-specific
|
|
57
|
+
hint and an **Open Settings** button that opens the Settings drawer directly.
|
|
58
|
+
It disappears automatically once the user selects a publisher / solution (or
|
|
59
|
+
switches to *All Entities*) — no dismiss cookie required, because the
|
|
60
|
+
condition is purely reactive to the persisted `DisplaySettings` state.
|
|
61
|
+
|
|
62
|
+
- **`OpenSettingsProvider` / `useOpenSettings` / `useRegisterOpenSettings`**
|
|
63
|
+
(`src/host/useOpenSettings.tsx`) — new React context that provides a
|
|
64
|
+
stable `() => void` callback to open the Settings drawer from any component
|
|
65
|
+
in the tree without prop-drilling. Uses a ref-based registration pattern
|
|
66
|
+
(zero provider re-renders). `FrameHeader` registers the callback on mount;
|
|
67
|
+
any consumer calls `useOpenSettings()` to get it.
|
|
68
|
+
|
|
69
|
+
- **`useScopedEntities` now exposes `needsSetup: boolean` and
|
|
70
|
+
`scopeMode: EntityScopeMode`** — consumers can detect the
|
|
71
|
+
unconfigured-scope condition and tailor guidance text accordingly.
|
|
72
|
+
|
|
73
|
+
### 🔍 Settings persistence confirmation
|
|
74
|
+
|
|
75
|
+
- Verified that all `DisplaySettings` (scope mode, selected publisher /
|
|
76
|
+
solution IDs, display flags) are persisted via `window.toolboxAPI.settings`
|
|
77
|
+
under the namespaced key `pptb-dataverse-request-studio:displaySettings`.
|
|
78
|
+
The prefix is distinct from other PPTB tools (e.g. FetchXML Studio). No
|
|
79
|
+
changes to the persistence layer were required.
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
8
83
|
## [1.0.0] - 2026-05-24
|
|
9
84
|
|
|
10
85
|
Initial public release of Dataverse Request Studio — a metadata-driven studio
|