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
Copy file name to clipboardExpand all lines: powerapps-docs/developer/data-platform/org-service/generate-early-bound-classes.md
+29-21Lines changed: 29 additions & 21 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Generate early-bound classes for the Organization service (Microsoft Dataverse) | Microsoft Docs"# Intent and product brand in a unique string of 43-59 chars including spaces
3
3
description: "Learn about a command-line code generation tool for use with Microsoft Dataverse. This tool generates early-bound .NET Framework classes that represent the Entity Data Model used by Dataverse."# 115-145 characters including spaces. This abstract displays in the search result.
4
-
ms.date: 04/03/2022
4
+
ms.date: 12/21/2022
5
5
author: kkanakas
6
6
ms.author: kartikka
7
7
manager: pemikkel
@@ -97,7 +97,7 @@ CrmSvcUtil.exe ^
97
97
- For the `username` and `password` parameters, type the user name and password that is used to sign in to Dataverse.
98
98
- For the `url` parameter, you can look up the correct URL in the web application by selecting **Settings**, navigating to **Customizations**, and then choosing **Developer Resources**. The URL is shown under **Organization Service**.
99
99
100
-
To list the supported command-line parameters, use the following command.
100
+
To view the latest supported command-line parameters, use the following command.
101
101
102
102
```ms-dos
103
103
CrmSvcUtil.exe /?
@@ -109,24 +109,32 @@ CrmSvcUtil.exe /?
109
109
110
110
The following table lists the code generation tool parameters and a gives a brief description of their use.
111
111
112
-
|Parameter|Shortcut|Description|Required|
113
-
|--|--|--|--|
114
-
|`deviceid`|`di`|No longer needed|False|
115
-
|`devicepassword`|`dp`|No longer needed|False|
116
-
|`___domain`|`d`|The ___domain to authenticate against when you connect to an on-premises server.|False|
117
-
|`url`||The URL for the Organization service.|True unless you use `interactivelogin`|
118
-
|`out`|`o`|The file name for the generated code.|True|
119
-
|`language`|`l`|The language to generate the code in. This can be either “CS” or “VB”. The default value is “CS”.|False|
120
-
|`namespace`|`n`|The namespace for the generated code. The default is the global namespace.|False|
121
-
|`username`|`u`|The user name to use when you connect to the server for authentication.|False|
122
-
|`password`|`p`|The password to use when you connect to the server for authentication.|False|
123
-
|`servicecontextname`||The name of the generated organization service context class. If no value is supplied, no service context is created.|False|
124
-
|`help`|`?`|Show usage information.|False|
125
-
|`nologo`||Suppress the banner at runtime.|False|
126
-
|`generateActions`||Generate request and response classes for custom actions.|False|
127
-
|`interactivelogin`|`il`|When used, a dialog to log into the Dataverse service is displayed. All other connection related parameters specified on the command line are ignored.|False|
128
-
|`connectionstring`|`connstr`|Contains information, provided as a single string, for connecting to a Dataverse organization. All other connection related parameters specified on the command line are ignored. For more information see [Use connection strings in XRM tooling to connect to Dataverse](../xrm-tooling/use-connection-strings-xrm-tooling-connect.md).|False|
129
-
112
+
|Parameter|Shortcut|Description|
113
+
|--|--|--|
114
+
|`url`||The URL for the Organization service. Required, unless you use `interactivelogin`|
115
+
|`out`|`o`|The file name for the generated code. Required|
116
+
|`language`|`l`|The language to generate the code in. This can be either “CS” or “VB”. The default value is “CS”.|
117
+
|`namespace`|`n`|The namespace for the generated code. The default is the global namespace.|
118
+
|`username`|`u`|The user name to use when you connect to the server for authentication.|
119
+
|`password`|`p`|The password to use when you connect to the server for authentication.|
120
+
|`___domain`|`d`|The ___domain to authenticate against when you connect to an on-premises server.|
121
+
|`servicecontextname`||The name of the generated organization service context class. If no value is supplied, no service context is created.
122
+
|`help`|`?`|Show usage information.|
123
+
|`nologo`||Suppress the banner at runtime.|
124
+
|`generateActions`||Generate request and response classes for custom actions.|
125
+
|`interactivelogin`|`il`|When used, a dialog to log into the Dataverse service is displayed. All other connection related parameters specified on the command line are ignored.|
126
+
|`connectionstring`|`connstr`|Contains information, provided as a single string, for connecting to a Dataverse organization. All other connection related parameters specified on the command line are ignored. For more information see [Use connection strings in XRM tooling to connect to Dataverse](../xrm-tooling/use-connection-strings-xrm-tooling-connect.md).|
127
+
|`suppressGeneratedCodeAttribute`|`sgca`|Suppresses the GeneratedCodeAttribute on all classes|
128
+
|`emitfieldsclasses`|`emitfc`|Generate a Fields class per entity that contains all of the field names at the time of code generation|
129
+
|`entitynamesfilter`||Filters the list of entities retrieved when reading data from Dataverse. Passed in as a semicolon separated list using the form <entitylogicalname>;<entitylogicalname>;...|
130
+
|`messagenamesfilter`||Filters the list of messages that are retrieved when reading data from Dataverse. Passed in as a semicolon separated list. Required messages ( Create, Update, Delete, Retrieve, RetrieveMultiple, Associate and DisAssociate) are always included. A * can be used to proceed or trail a message allowing for all messages starting with or ending with a string. The list takes the form <messagename>;<messagename>;...|
131
+
|`splitfiles`||Splits the output into files by type, organized by entity, message, and optionsets. when enabled, the `out` property is ignored and `outdirectory` is required instead|
132
+
|`outdirectory`|`outdir`|Write entity, message and optionset files to a specified output directory. Valid only with the `splitfiles` option|
133
+
|`entitytypesfolder`||Folder name that will contain entities. THe default folder name is "Entities". Valid only with the `splitfiles` option.|
134
+
|`messagestypesfolder`||Folder name that will contain messages. The default name is "Messages". Valid only with the `splitfiles` option|
135
+
|`optionsetstypesfolder`||Folder name that will contain optionsets. The default name is "OptionSets". Valid only with `splitfiles` option|
136
+
|`generateGlobalOptionSets`||Emit all global optionsets. Note: if an entity contains a reference to a global optionset, it will be emitted even if this switch is not present|
137
+
|`legacyMode`||Disable emitting optionsets and many newer code features to support compatibility with older custom extensions|
130
138
131
139
<aname="bkmk_sampleconfig"></a>
132
140
@@ -175,7 +183,7 @@ For more information on supported tracing options see [Configure tracing for XRM
175
183
176
184
### See Also
177
185
178
-
[Late-bound and early-bound programming using the Organization service](early-bound-programming.md)
186
+
[Late-bound and early-bound programming](early-bound-programming.md)
0 commit comments