Skip to content

Commit a7b0c97

Browse files
committed
edit
1 parent 2bf6aae commit a7b0c97

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

powerapps-docs/developer/data-platform/custom-api.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,14 +3,15 @@ title: "Create and use custom APIs (Microsoft Dataverse) | Microsoft Docs" # Int
33
description: "custom API is a code-first way to define custom messages for Microsoft Dataverse" # 115-145 characters including spaces. This abstract displays in the search result.
44
author: divkamath
55
ms.author: dikamath
6-
ms.date: 10/18/2023
6+
ms.date: 02/14/2024
77
ms.reviewer: jdaly
88
ms.topic: article
99
ms.subservice: dataverse-developer
1010
search.audienceType:
1111
- developer
1212
contributors:
1313
- JimDaly
14+
- SomaDaDe
1415
---
1516
# Create and use custom APIs
1617

@@ -477,11 +478,13 @@ To debug using the Plug-in Registration tool and the Plug-in profiler solution,
477478

478479
If you define your custom API to be private, you can't use that message in a plug-in. More information: [Private Messages](org-service/use-messages.md#private-messages)
479480

480-
### Secure Configuration and Unsecure Configuration cannot be sent in CustomAPI Main Operation plug-in
481+
### Secure and Unsecure Configuration cannot be set for the Custom API Main Operation plug-in
481482

482-
You cannot pass [Secure and Unsecure Configuration](write-plug-in.md#pass-configuration-data-to-your-plug-in) in to your Stage 30 Main operation Plugin for the CustomAPI.
483+
You cannot pass [Secure and Unsecure Configuration](write-plug-in.md#pass-configuration-data-to-your-plug-in) in to the Main operation Plugin for the CustomAPI.
483484

484-
**Workaround**: Do not register the plugin, where you want send the secure and unsecure configuration, during CustomAPI creation through UI. Register the plugin as a `PreOperation` or `PostOperation` plugin through PRT and you should be able to set the configuration values as any other plug-in. More information: [Register Plug-in and set configuration data](register-plug-in.md#set-configuration-data)
485+
**Workaround**: Rather than associate the plug-in with the Custom API, register the plug-in on the `PostOperation` stage using the Plug-in Registration tool (PRT). This way, you can [specify configuration data in the `PostOperation` plug-in step as you usually do](register-plug-in.md#set-configuration-data).
486+
487+
For this to work, you must configure your Custom API to enable **Sync and Async** [custom processing step types](#select-a-custom-processing-step-type) when you create the custom api. You can't change this after you create it.
485488

486489
### Next Steps
487490

0 commit comments

Comments
 (0)