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/troubleshoot-plug-in.md
+5-3Lines changed: 5 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "Troubleshoot plug-ins (Common Data Service for Apps) | Microsoft Docs"# Intent and product brand in a unique string of 43-59 chars including spaces
3
3
description: "Contains information on errors that can occur due to plug-ins and how to fix them."# 115-145 characters including spaces. This abstract displays in the search result.
4
4
ms.custom: ""
5
-
ms.date: 04/21/2019
5
+
ms.date: 04/26/2019
6
6
ms.reviewer: ""
7
7
ms.service: "powerapps"
8
8
ms.topic: "article"
@@ -25,7 +25,9 @@ Error Code: `-2147220911`<br />
25
25
Error Message: `There is no active transaction. This error is usually caused by custom plug-ins that ignore errors from service calls and continue processing.`
26
26
27
27
This can be a difficult error to address because the cause can be in someone else's code. To understand the message, you need to appreciate that any time an error related to a data operation occurs within a synchronous plug-in the transaction for the entire operation will be ended.
28
-
[Scalable Customization Design in Common Data Service](scalable-customization-design/overview.md)
28
+
29
+
More information: [Scalable Customization Design in Common Data Service](scalable-customization-design/overview.md)
30
+
29
31
The most common cause is simply that a developer might believe they can attempt to perform an operation that *might* succeed so they wrap that operation in a try/catch block and attempt to swallow the error if it fails.
30
32
31
33
While this may work for a client application, within the execution of a plug-in any data operation failure will result in rolling back the entire transaction. You can't swallow the error, so you must make sure to always return an <xref:Microsoft.Xrm.Sdk.InvalidPluginExecutionException>.
@@ -67,4 +69,4 @@ You can register the plug-in to run in the context of a user known to have the c
67
69
68
70
<!-- But if you prefer that the logic in your plug-in adapt to the privileges that the calling user has, you really need to verify the user's privileges in your code.
This topic describes how to write an Azure solution listener application that can read and process Dynamics 365 (online) Common Data Service messages that are posted to the Azure Service Bus. As a prerequisite, you should familiarize yourself with how to write a Azure Service Bus listener before trying to learn the specifics of a Dynamics 365 listener. For more information, see the [Azure Service Bus documentation](https://azure.microsoft.com/en-us/documentation/services/service-bus/).
28
26
29
27
<aname="bkmk_writequeued"></a>
@@ -42,7 +40,7 @@ A *topic* is similar to a queue but implements a publish/subscribe model. One or
42
40
> [!IMPORTANT]
43
41
> To use these queue or topic contracts, you must write your listener applications using the [Azure SDK](http://azure.microsoft.com/downloads/archive-net-downloads/) version 1.7 or higher.
44
42
45
-
Use of queues and topics in your multi-system software design can result in the decoupling of systems. If the listener application ever becomes unavailable, the message delivery from Dynamics 365 will still succeed and the listener application can continue processing the queue message when it is back online. [!INCLUDEMore information [Queues, Topics, and Subscriptions](https://docs.microsoft.com/azure/service-bus-messaging/service-bus-queues-topics-subscriptions)
43
+
Use of queues and topics in your multi-system software design can result in the decoupling of systems. If the listener application ever becomes unavailable, the message delivery from Dynamics 365 will still succeed and the listener application can continue processing the queue message when it is back online. More information:[Queues, Topics, and Subscriptions](https://docs.microsoft.com/azure/service-bus-messaging/service-bus-queues-topics-subscriptions)
46
44
47
45
<aname="bkmk_writeoneway"></a>
48
46
@@ -143,4 +141,4 @@ else if (receivedMessage.ContentType = "application/xml")
Copy file name to clipboardExpand all lines: powerapps-docs/maker/canvas-apps/working-with-environments.md
+8-16Lines changed: 8 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -17,9 +17,9 @@ search.app:
17
17
# Working with environments and Microsoft PowerApps
18
18
With PowerApps, you can work in different environments and easily switch among them. For an overview of environments, see [Environments overview](../../administrator/environments-overview.md), which explains in detail why you use environments and how you can create and manage them. The scope of this article will cover the following topics on environment:
19
19
20
-
* how to switch the environment on powerapps.com
21
-
* how to create an app in the right environment
22
-
* how to view an app in the right environment
20
+
- how to switch the environment on powerapps.com
21
+
- how to create an app in the right environment
22
+
- how to view an app in the right environment
23
23
24
24
## Switch the environment
25
25
When you sign up and first sign in to powerapps.com, you will likely land in a default environment. You can verify this by looking at the upper-right corner of the page.
@@ -35,23 +35,15 @@ Once you switch to a different environment (such as Environment 1), you will see
35
35
## Create apps in the right environment
36
36
You can create apps in an environment that you create or for which you've been given access. Creating your own environment, however, requires a [specific plan](../../administrator/pricing-billing-skus.md). Before you create an app, always **make sure you select the environment you want to app to be in**. Otherwise, you will have to deal with moving apps between environments.
37
37
38
-
To create an app in the right environment, do either of the following:
38
+
To create an app in the right environment:
39
39
40
-
- If PowerApps Studio isn't open, [sign in](http://web.powerapps.com?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), select the environment you would like to create your app in, select **Apps** near the left edge, and then select **Create an app**.
40
+
1.[Sign in to PowerApps](http://web.powerapps.com?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc).
41
41
42
-
- If PowerApps Studio is open, select the environment again at the top right corner.
42
+
1. As the previous section describes, select the environment in which you would like to create your app.
43
43
44
-
5. On the **Account** page, select **Change** next to the name of the current environment.
45
-
46
-
6. Select the environment you want to create your app in.
1. Select **Apps** near the left edge, and then select **Create an app**.
53
45
54
46
## View apps in the right environment
55
-
Whether you are working in [powerapps.com](http://web.powerapps.com?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) or PowerApps Studio, the list of apps, connections, etc. that you see is always filtered based on the environment that's selected in the dropdown. If you don't see the apps you are looking for, always confirm whether the right environment is selected.
47
+
Whether you are working in [powerapps.com](http://web.powerapps.com?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) or PowerApps Studio, the list of apps, connections, etc. that you see is always filtered based on the environment that's selected in the dropdown. If you don't see the apps you're looking for, always confirm whether the right environment is selected.
56
48
57
49
For more information about environments, see [this overview](../../administrator/environments-overview.md).
0 commit comments