Generated typed service class<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n![\"Dataverse\"](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/05\/Dataverse-6.png\") <\/h3>\nStep 3: Use the Generated Services in Your App<\/h3>\n
With the service classes generated, you can now import and call them directly in your application code. The CLI handles all the Web API URL construction, authentication headers, and response parsing behind the scenes.<\/p>\n Calling WhoAmI<\/h3>\nImport the WhoAmIService from the generated services directory and call it to retrieve the current user’s identity:<\/p>\n import { WhoAmIService } from '.\/generated\/services\/WhoAmIService';\r\n\r\nconst userInfo = await WhoAmIService.WhoAmI() as any;\r\n\r\nconst currentUserId = userInfo.UserId;\r\n\r\nconst businessUnitId = userInfo.BusinessUnitId;\r\n\r\nconst orgId = userInfo.OrganizationId;<\/pre>\nThe result object contains three GUIDs \u2014 UserId, BusinessUnitId, and OrganizationId \u2014 all fully typed. In the case routing app, we use the UserId to display which agent is currently logged in, giving the team lead confidence before performing any routing action.<\/p>\n Calling PickFromQueue<\/h3>\nThe PickFromQueue action is a bound operation, which means the generated service method takes the queue item GUID as its first argument, followed by the operation parameters:<\/p>\n import { PickFromQueueService } from '.\/generated\/services\/PickFromQueueService';\r\nconst handlePickCase = async (queueItemId: string, currentUserId: string) => {\r\n\r\nconst systemUser = {\r\n\r\n'@odata.type': 'Microsoft.Dynamics.CRM.systemuser',\r\n\r\nsystemuserid: currentUserId\r\n\r\n};\r\n\r\nawait PickFromQueueService.PickFromQueue(\r\n\r\nqueueItemId,\u00a0\u00a0\u00a0 \/\/ GUID of the queue item (first arg for bound actions)\r\n\r\nsystemUser,\u00a0\u00a0\u00a0\u00a0 \/\/ The system user to assign the case to\r\n\r\ntrue\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ RemoveQueueItem \u2014 remove from queue after picking\r\n\r\n);\r\n\r\nconsole.log('Case picked from queue successfully');\r\n\r\n};<\/pre>\nThe function picks the case from the queue and assigns it to the specified user. When RemoveQueueItem is true, the item is automatically removed from the queue to prevent duplicate assignments.<\/p>\n Note: <\/strong>For bound operations, the first argument is always the GUID of the record the action is bound to. In this case, PickFromQueue is bound to mscrm.queueitem, so the first argument is the queue item ID.<\/em><\/p><\/blockquote>\nStep 4: Build the Case Routing UI<\/h3>\nWith both services wired up, the final step is to build the actual interface the team leads will use. The component needs to show a list of open cases, allow selection, and trigger the routing action.<\/p>\n Below is a simplified version of how the component comes together:<\/p>\n import { useEffect, useState } from 'react';\r\n\r\nimport { WhoAmIService } from '.\/generated\/services\/WhoAmIService';\r\n\r\nimport { PickFromQueueService } from '.\/generated\/services\/PickFromQueueService';\r\n\r\n\/\/ Sample cases in queue (in production, fetch from Dataverse)\r\n\r\nconst queuedCases = [\r\n\r\n{ id: 'CAS-1001', title: 'Printer not working',\u00a0\u00a0\u00a0 queueItemId: '< queue-item-guid-1 >' },\r\n\r\n{ id: 'CAS-1002', title: 'Password reset request', queueItemId: '< queue-item-guid-2 >' },\r\n\r\n{ id: 'CAS-1003', title: 'Software installation',\u00a0 queueItemId: '< queue-item-guid-3 >' },\r\n\r\n];\r\n\r\nexport const CaseRoutingApp = () => {\r\n\r\nconst [currentUserId, setCurrentUserId] = useState('');\r\n\r\nconst [routedCases, setRoutedCases] = useState<Record<string, boolean>>({});\r\n\r\nuseEffect(() => {\r\n\r\nWhoAmIService.WhoAmI().then((r: any) => setCurrentUserId(r.UserId));\r\n\r\n}, []);\r\n\r\nconst handlePickCase = async (queueItemId: string, caseId: string) => {\r\n\r\nconst systemUser = {\r\n\r\n'@odata.type': 'Microsoft.Dynamics.CRM.systemuser',\r\n\r\nsystemuserid: currentUserId\r\n\r\n};\r\n\r\nawait PickFromQueueService.PickFromQueue(queueItemId, systemUser, true);\r\n\r\nsetRoutedCases(prev => ({ ...prev, [caseId]: true }));\r\n\r\n};\r\n\r\nreturn ( \/* your JSX here *\/ );\r\n\r\n};\r\n\r\n![\"Dataverse](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/05\/Dataverse-7.png\") <\/pre>\nOnce you are happy with the result in local preview, run:<\/p>\n npx power-apps push<\/pre>\nThis deploys the app to your Dataverse environment and makes it available inside the model-driven app.<\/p>\n Important Notes and Common Pitfalls<\/h3>\nA few things to keep in mind as you work with this feature:<\/p>\n Bound vs. Unbound Operations<\/h3>\nThe distinction between bound and unbound operations matters for how you call the generated service method. Bound operations always take an id: string as the first argument (the GUID of the record the operation is bound to). Unbound operations, like WhoAmI, take only the declared parameters.<\/p>\n The CLI detects the operation type automatically and generates the method signature accordingly. You do not need to configure anything manually.<\/p>\n Re-running add-dataverse-api is Safe<\/h3>\nIf the operation’s signature changes in your environment \u2014 for example, a developer added a new optional parameter \u2014 simply re-run the same command:<\/p>\n npx power-apps add-dataverse-api --api-name PickFromQueue<\/pre>\nThe command is idempotent. It overwrites the schema and regenerates the service class with the latest definition. It will not create duplicate entries in power.config.json, and it will not overwrite entity schema files that already exist.<\/p>\n Conclusion<\/strong><\/h3>\nThe add-dataverse-api command is a significant quality-of-life improvement for developers building Power Apps code apps. Instead of handwriting Web API calls, managing URL patterns for bound vs. unbound operations, and manually typing response objects, you get fully generated, type-safe service classes in seconds.<\/p>\n For the support team in our scenario, the result was exactly what the client needed. Cases are now routed with a single click, the correct agent identity is confirmed before any action is taken, and the development time was a fraction of what it would have taken with raw Web API calls.<\/p>\n Whether you are calling WhoAmI to verify the current session, triggering a bound action like PickFromQueue to execute business logic, or invoking a custom operation your team has built, the CLI handles the scaffolding so you can focus on building the experience.<\/p>\n FAQs<\/h3>\nWhat is add-dataverse-api in Power Apps code apps?<\/strong><\/p>\nThe add-dataverse-api command is a Power Apps CLI feature that generates fully typed TypeScript service classes for Dataverse actions and functions. It eliminates the need to manually write Web API fetch calls when building Power Apps code apps.<\/p>\n How do you call Dataverse actions from a Power Apps code app?<\/strong><\/p>\nYou can call Dataverse actions in a Power Apps code app by using the Power Apps npm CLI commands find-dataverse-api and add-dataverse-api. These commands generate typed service classes that let developers invoke Dataverse actions directly in TypeScript.<\/p>\n What is the difference between bound and unbound Dataverse actions?<\/strong><\/p>\nBound Dataverse actions are linked to a specific Dataverse table or record and require a record GUID as the first parameter. Unbound actions are standalone operations that do not require a record reference. For example, PickFromQueue is bound, while WhoAmI is unbound.<\/p>\n
| ![\"Dataverse\"](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/05\/Calling-Dataverse-Actions-and-Functions-from-Power-Apps-Code-Apps.png\")
When building Power Apps code apps, one of the most powerful things you can do is reach directly into Dataverse to trigger business logic. Whether it is routing a support ticket to the right queue, checking who the current user is, or running a custom API operation, Dataverse actions and functions are the engine behind most enterprise workflows.<\/p>\n![\"Dataverse](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/05\/Dataverse-1.png\")
<\/p>\n![\"Dataverse\"](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/05\/Dataverse-2.png\")
<\/h3>\n![\"Dataverse\"](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/05\/Dataverse-3.png\")
<\/p>\n![\"Dataverse](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/05\/Dataverse-4.png\")
<\/p>\n![\"Dataverse](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/05\/Dataverse-5.png\")
<\/p>\n