Skip to content

Latest commit

 

History

History
52 lines (37 loc) · 2.57 KB

object-checker.md

File metadata and controls

52 lines (37 loc) · 2.57 KB
Raw
title description Keywords author ms.author ms.reviewer ms.date ms.topic search.audienceType
Use object checker in solutions | MicrosoftDocs
Use object checker to run live analysis of potential issues with objects in your solution.
object checker, checker, solution checker, solution issue
caburk
caburk
matp
04/25/2023
how-to
maker

Use object checker to diagnose a solution component (preview)

[!INCLUDE cc-beta-prerelease-disclaimer]

Object checker runs real-time diagnostics on component objects within your solution. If issues are detected, a recommendation is returned that describes how to fix the issue. This might include documentation, instructions, or a click-able action that can fix the issue for you.

Example issues object checker detects

  • Active layer hiding customizations.
  • Malformed or corrupted metadata.

Run object checker and view the results

  1. Sign into Power Apps, and then select Solutions from the left navigation pane. [!INCLUDE left-navigation-pane]

  2. Open a solution that contains the problematic object. You can run object checker within either managed and unmanaged solutions.

  3. Select a single object, such as a model-driven app or a site map.

  4. On the command bar, select ... > Object checker > Run. :::image type="content" source="media/object-checker-run.png" alt-text="Run object checker":::

  5. When object checker finishes, on the command bar, select ... > Object checker > View results :::image type="content" source="media/object-checker-view-results.png" alt-text="View object checker results":::

  6. The results are displayed in the right pane. If issues are detected, follow the prompt to resolve the issue.

  7. Select Close to close the object checker results pane.

Current limitations

  • Object checker currently only works with model-driven app and site map components.

  • Object Checker rules might fail if customizations haven't been published. When this condition occurs, the following exception can be observed in the 'Multiple sitemaps detection rule':

    Exception encountered while executing rule: System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: The value passed for ConditionOperator.In is empty.

See also

Tools available to diagnose solutions

[!INCLUDEfooter-include]