Skip to content

Commit f2a39d6

Browse files
authored
Merge pull request #3669 from MicrosoftDocs/master-jdaly-2020-10-27
Master jdaly 2020 10 27
2 parents 06937df + d0ffd9b commit f2a39d6

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

powerapps-docs/developer/common-data-service/custom-api.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
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
33
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.
44
ms.custom: ""
5-
ms.date: 10/26/2020
5+
ms.date: 10/27/2020
66
ms.reviewer: "pehecke"
77
ms.service: powerapps
88
ms.topic: "article"
@@ -347,6 +347,12 @@ A: Your private messages will work regardless of whether they are advertised in
347347

348348
Custom APIs are a preview feature and subject to change. Following are some known issues we expect to change.
349349

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+
350356
### A custom API cannot be called from a workflow
351357

352358
A Workflow Custom Action can be called from another workflow. Currently, Custom APIs cannot.

0 commit comments

Comments
 (0)