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/common-data-service/custom-api.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "Create and use Custom APIs (Common Data Service) | Microsoft Docs"# Intent and product brand in a unique string of 43-59 chars including spaces
3
3
description: "Custom API is a new code-first way to define custom messages for the Common Data Service"# 115-145 characters including spaces. This abstract displays in the search result.
4
4
ms.custom: ""
5
-
ms.date: 10/26/2020
5
+
ms.date: 10/27/2020
6
6
ms.reviewer: "pehecke"
7
7
ms.service: powerapps
8
8
ms.topic: "article"
@@ -347,6 +347,12 @@ A: Your private messages will work regardless of whether they are advertised in
347
347
348
348
Custom APIs are a preview feature and subject to change. Following are some known issues we expect to change.
349
349
350
+
### Not able to use profiler for debugging
351
+
352
+
To debug using the Plug-in Registration tool and the Plug-in profiler solution, you need to be able to select a specific plug-in step. The main stage implementation for the plug-in is not available in the Plug-in Registration tool.
353
+
354
+
**Workaround**: Register the plug-in type on the PostOperation stage of the message created for the Custom API.
355
+
350
356
### A custom API cannot be called from a workflow
351
357
352
358
A Workflow Custom Action can be called from another workflow. Currently, Custom APIs cannot.
0 commit comments