Skip to content

Commit 486a58e

Browse files
committed
Merge branch 'master' into sampleapps-2061766
2 parents a56decf + ba25084 commit 486a58e

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

powerapps-docs/developer/common-data-service/org-service/organizationservicecontext.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ contact.EMailAddress1 = “[email protected]”;
144144

145145
When creating a new entity record, you add the object to the organization service context by using the <xref:Microsoft.Xrm.Sdk.Client.OrganizationServiceContext.AddObject(Microsoft.Xrm.Sdk.Entity)>. method.
146146

147-
The following sample shows how to instantiate and save a new contact record by using the entity data model. It also demonstrates how tp access a custom attribute.
147+
The following sample shows how to instantiate and save a new contact record by using the entity data model. It also demonstrates how to access a custom attribute.
148148

149149
```csharp
150150
OrganizationServiceContext orgContext =new OrganizationServiceContext(svc);
@@ -198,4 +198,4 @@ To delete an entity record, the organization service context must be tracking th
198198
[LINQ query examples using OrganizationServiceContext with Common Data Service](linq-query-examples.md)<br />
199199
[Generate classes for early-bound programming using the Organization service](generate-early-bound-classes.md)<br />
200200
<xref:Microsoft.Xrm.Sdk.IOrganizationService><br />
201-
<xref:Microsoft.Xrm.Sdk.Client.OrganizationServiceContext>
201+
<xref:Microsoft.Xrm.Sdk.Client.OrganizationServiceContext>

powerapps-docs/maker/common-data-service/common-issues-resolutions-solution-checker.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -265,7 +265,7 @@ Solution checker supports global variables for ECMAScript 2015 (ES6) and up to E
265265

266266
For plug-in and workflow activity rules where the issue is only relevant in the calling context, the solution checker tool starts its analysis at the IPlugin interface implementation and traverses a call graph to detect issues within the scope of that implementation. In some cases, many call paths may arrive at the same ___location where the issue is detected. Since the issue is relevant to the call scope, the tool may report based on that scope to provide a better picture of impact rather than on distinct locations. As a result, multiple issues may reference a single ___location that should be fixed.
267267

268-
## app-formula-issues-high and app-formula-issues-high may show different number of errors than those shown in design mode
268+
## app-formula-issues-high may show different number of errors than those shown in design mode
269269

270270
The solution checker will list the number of the errors found in the app, *including those from tests*. The app checker in design mode only shows errors from screen controls and components. If the error count shown in the app checker in design mode is smaller, open the [Test Studio](../canvas-apps/test-studio.md) and search for the errors in the expressions used in tests.
271271

0 commit comments

Comments
 (0)