Skip to content

Commit 090fb29

Browse files
committed
Linking APIs
1 parent 02fcbd1 commit 090fb29

File tree

1 file changed

+2
-16
lines changed
  • powerapps-docs/developer/model-driven-apps/clientapi/reference/events

1 file changed

+2
-16
lines changed

powerapps-docs/developer/model-driven-apps/clientapi/reference/events/postsave.md

Lines changed: 2 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -20,15 +20,10 @@ search.app:
2020

2121
PostSave event occurs after the `OnSave` event is complete. This event is used to support or execute custom logic using web resources to perform after `Save` actions when the `save` event is successful or failed due to server errors.
2222

23-
Use the `addOnPostSave` method to manage event handlers for this event.
23+
Use the [addOnPostSave](../controls/addOnPostSave.md) and [removeOnPostSave](../controls/removeOnPostSave.md) methods to manage event handlers for this event.
2424

2525
> [!NOTE]
26-
> This method is supported only on Unified Interface.
27-
28-
<!--Some of the post save events include which are used by one of the first party app Field Service.
29-
1) When we create a work order incident, read incident type, and retrieve all incident products where incident type is equal to incident type on work order incident, then create work order products.
30-
2) If work order incident is primary incident on work order, modifying the work order incident that is updates the primary inc
31-
When a primary contact phone number is updated, update the same on the account phone number.-->
26+
> This method is supported only on Unified Interface
3227
3328
## Syntax
3429

@@ -43,15 +38,6 @@ When a primary contact phone number is updated, update the same on the account p
4338

4439
[!INCLUDE[cc-terminology](../../../../data-platform/includes/cc-terminology.md)]
4540

46-
<!--Code Example:
47-
We call below method and it will display org name. For making decisions on whether the save succeeded or failed, executioncontext object will have params such as
48-
1) getIsSaveSuccess() - use this method to know if the save operation on the entity succeeds or fails
49-
Usage - executionContext.getEventArgs(). getIsSaveSuccess();
50-
2) getEntityReference() - it will have entity info being saved/updated in case of success such as entity id, entity name (for eg., account or contact)
51-
Usage - executionContext.getEventArgs(). getEntityReference();
52-
3) getSaveErrorInfo() - Error details on why an entity save failed.
53-
Usage - executionContext.getEventArgs(). getSaveErrorInfo ();-->
54-
5541
### Example
5642

5743
The following sample code displays organization unique name as form notification.

0 commit comments

Comments
 (0)