You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Added entity attribute metadata for enabling more features with typings [`#228`](https://github.com/Power-Maverick/DataverseDevTools-VSCode/pull/228)
15
22
23
+
### Commits
24
+
25
+
- Docs: Add @uofirob as a contributor [`61b0edd`](https://github.com/Power-Maverick/DataverseDevTools-VSCode/commit/61b0edd8fdb714c872711e58f94028c6934d69a5)
26
+
- Bump version to 2.2.3 and merge entity attribute [`621ea2e`](https://github.com/Power-Maverick/DataverseDevTools-VSCode/commit/621ea2eb986bb360920b576bbd0ca6470315648d)
27
+
- Docs: Update @uofirob as a contributor [`2464a03`](https://github.com/Power-Maverick/DataverseDevTools-VSCode/commit/2464a035dda9aa7e28495466be12b8c6a1befbd8)
|Username & Password | This works with environments without MFA-enabled and needs no extra configuration. |
92
-
|Microsoft Login Prompt | Uses DVDT's Public App registered in Azure AD. This will need approval from Azure Admin before you can use it for authentication. This connection other than approving the public Azure AD app (which is a one-time activity) needs no extra configuration. This connection will work with MFA-enabled authentication as well.|
93
-
| Client Id & Secret | This works with MFA-enabled authentication but needs extra configuration of Azure AD App Registration. To know more on app registration process [read here](https://docs.microsoft.com/en-us/powerapps/developer/data-platform/walkthrough-register-app-azure-active-directory?WT.mc_id=BA-MVP-5003877). |
94
-
| Azure | If you are already logged in inside VSCode using Az extension, Azure CLI or Azure PowerShell, you can leverage Azure Identity Framework to get authenticated against Dataverse. The developer has to use the same account for both Azure and Power Platform for this work (thanks to [Natraj Yegnaraman](https://github.com/rajyraman) for this method). This is a single-click authentication method with no prompts. |
|Microsoft Login Prompt (Recommended) | Uses Microsoft Dev App Id. This connection will work with MFA-enabled authentication as well.|
95
+
|Username & Password | This works with environments without MFA-enabled and needs no extra configuration. |
96
+
| Client Id & Secret | This works with MFA-enabled authentication but needs extra configuration of Azure AD App Registration. To know more on app registration process [read here](https://docs.microsoft.com/en-us/powerapps/developer/data-platform/walkthrough-register-app-azure-active-directory?WT.mc_id=BA-MVP-5003877). |
97
+
| Azure | If you are already logged in inside VSCode using Az extension, Azure CLI or Azure PowerShell, you can leverage Azure Identity Framework to get authenticated against Dataverse. The developer has to use the same account for both Azure and Power Platform for this work (thanks to [Natraj Yegnaraman](https://github.com/rajyraman) for this method). This is a single-click authentication method with no prompts. |
95
98
96
99
Below is one of the way you can create the connection.
97
100
@@ -171,10 +174,15 @@ You can launch your favorite Power Platform tools right from VSCode. Below are t
171
174
172
175
## 🔥 Using Typings
173
176
177
+
## Generate Typing
178
+
174
179
1. Go to **Dataverse DevTools** from the _Activity Side Bar_.
175
180
2. From the list of entities, right-click the entity for which you want to create a typing and choose `Generate Typings` option. You can also filter the list of entities by clicking the filter button on the Entities panel as shown [here](#filter-by-solution).
176
-
3. Create a onLoad function in your TypeScript file with parameter as `executionContext: Xrm.Events.EventContext`.
177
-
4. Initialize your `FormContext` global variable casting it with `Xrm.<entity name>`.
181
+
182
+
### When working with Xrm object from @types/xrm
183
+
184
+
1. Create a onLoad function in your TypeScript file with parameter as `executionContext: Xrm.Events.EventContext`.
185
+
2. Initialize your `FormContext` global variable casting it with `Xrm.<entity name>`.
178
186
179
187
For example:
180
188
If you wanted to use _Accounts_ entity typings in your TypeScript file then after the typings are generated the code in your TypeScript file will look as shown below:
@@ -188,6 +196,23 @@ export function onLoad(executionContext: Xrm.Events.EventContext) {
188
196
189
197
In the above code snippet, `Xrm.Account` is a typing generated by Dataverse DevTools to provide intellisense specific to the **Account** entity.
190
198
199
+
### When working with entity and attributes only
200
+
201
+
1. Just use by typings the entity name
202
+
203
+
For example:
204
+
If you wanted to use _Accounts_ entity typings in your TypeScript file then after the typings are generated the code in your TypeScript file will look as shown below:
All the Power Platform CLI commands are easily categorized in a tree format that enables you to execute them with a button-click. If any command needs a parameter then system will intelligently prompt for the input from you. At this time only **required** parameters will be prompted by the system. Please see it in action below:
Copy file name to clipboardExpand all lines: package.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
{
2
2
"name": "dataverse-devtools",
3
3
"displayName": "Dataverse DevTools",
4
-
"version": "2.2.3",
4
+
"version": "2.2.4",
5
5
"description": "The all-in-one tool to develop code for Dataverse/Dynamics 365. Helps you connect to a Dataverse environment, generate TypeScript definitions for entities, create different type of Dataverse-specific projects and much more.",
0 commit comments