Installation Guide

Overview

This guide walks administrators through installing and configuring the CT REx solution in a Microsoft Power Platform / Dynamics 365 environment.

This document is intended for tenant administrators and Power Platform administrators who can create or manage environments and install solutions.

Prerequisites

Before clicking Get it now in Microsoft AppSource, ensure the following requirements are met for the target tenant and environment:

Required permissions

  • One of the following directory roles:

    • Global Administrator (Tenant)

    • Power Platform Administrator

  • Ability to sign in with organizational (work) account.

If your organization uses delegated administration or Conditional Access, coordinate with your security team to ensure you can complete marketplace purchase and solution installation flows.

Environment type

  • Confirm which environment type your deployment policy allows. CT REx supports:

    • Production (recommended for live use)

    • Sandbox (recommended for testing/validation)

Install and validate in a Sandbox environment first, then promote the same version and configuration to Production.

Dataverse and Dynamics 365 apps

  • The target environment must:

    • Have a Microsoft Dataverse database provisioned.

    • Be Dynamics 365 apps enabled (e.g., Dynamics 365 Sales turned on for the environment).

Check this in Power Platform admin center → Environments → select your environment → verify Type, Region, Dataverse status, and Dynamics 365 apps are enabled.

Licensing

  • Users who will access CT REx features must have the appropriate licensing based on the part of the application they use:

    • Front‑end mobile users working in the CT REx Canvas App require a Power Apps per‑app license (or Pay‑as‑you‑go).

    • Users working with the CT REx Model‑Driven App require a Dynamics 365 Sales license (Enterprise or Premium, per your product licensing) and must have access to the model‑driven environment features..

  • Admin performing installation must be allowed to acquire AppSource offers (if installing from marketplace).

License assignment for end users can be completed after installation, but users won’t see CT REx functionality until correct licenses and security roles are assigned.

Plan your deployment

  1. Choose the environment (Sandbox first) and confirm it meets prerequisites.

  2. Identify who will install (Global Admin or Power Platform Admin).

  3. Schedule a change window if your organization requires one.

Install CT REx from AppSource

  1. Go to Microsoft AppSource and search for CT REx.

  2. Open the CT REx product page and click Get it now.

  3. Sign in with your work account if prompted.

  4. Review and accept the permissions and terms.

  5. Select the tenant and then the target environment (e.g., Contoso – Sandbox).

  6. Confirm and start installation.

The marketplace flow provisions the solution into your selected environment. This can take from a few minutes to over 30 minutes depending on dependencies and tenant load.

Monitor installation progress

  1. Open Power Platform admin center → Environments.

  2. Select the target environment → Resources → Dynamics 365 apps and Solutions.

  3. Verify that CT REx solution(s) appear and status progresses from Installing → Installed.

  4. If the solution includes dependent packages (managed solutions), ensure all show Installed with no errors.

Do not close the marketplace window until you see confirmation. If the browser session ends early, the background installation usually continues, but always verify status in Solutions.

Post-installation configuration

After the solution is installed, complete the following steps to make CT REx available to users:

Connection references (if applicable)

  1. In the target environment, go to Solutions → open the CT REx solution.

  2. Locate Connection references.

  3. For each required connector (e.g., Dataverse; any external connectors used by CT REx), click to Set connection or Create new connection.

  4. Authenticate as needed and save.

If connection references are missing or unresolved, flows and automations will not run.

Environment variables (if applicable)

  1. In the CT REx solution, locate Environment variables.

  2. Provide values for any required configuration keys (e.g., API base URLs, feature flags, default business unit IDs).

  3. Save and Publish all customizations.

Use Sandbox-specific values first. Document values so you can replicate configuration in Production.

Security roles

  1. Navigate to Advanced settings → Security → Security roles.

  2. Review the CT REx roles delivered by the solution (e.g., CT REx Admin, CT REx User).

  3. Assign roles to:

    • Admin/Operations staff who will configure CT REx.

    • Business users who will use CT REx features.

  4. If you use Azure AD groups, align role assignment with your identity group strategy.

Users must have both the correct Dynamics 365 license and the CT REx security role(s) to access features in the Dynamics app.

App access (model-driven app visibility)

  1. Go to Apps in the environment.

  2. Locate the CT REx app (if provided as a model-driven app).

  3. Share/publish the app to the appropriate security roles.

  4. Optionally pin the app to users’ app launcher.

Validate the installation

  1. Sign in as an administrator with CT REx Admin role.

  2. Open the CT REx app or the Dynamics 365 app where CT REx features are surfaced.

  3. Validate:

    • Navigation and sitemap entries render.

    • Tables, forms, and views load.

    • Flows/automations (if any) are turned on and run without errors.

    • Connection references show Connected.

  4. Sign in as a business user with CT REx User role to confirm expected permissions and UI access.

Upgrading CT REx

  1. When a new version is released:

    1. Review release notes.

    2. Schedule a maintenance window.

    3. In Solutions, select the CT REx solution with Update available → Update.

    4. Re-validate connection references and environment variables (new versions may add or change these).

    5. Publish all customizations and test.

If you deploy via AppSource private plans or managed distribution, follow your organization’s internal promotion process (Dev → Test → Prod) and ensure version alignment across environments.

Uninstalling CT REx

Uninstalling a managed solution removes its components. Data stored in custom tables might also be impacted depending on solution design. Back up the environment or export data if needed.

  1. Go to Solutions in the target environment.

  2. Select the CT REx managed solution → Uninstall.

  3. Follow prompts. If dependencies exist, remove dependent items first or uninstall add-ons in reverse order of installation.

Troubleshooting

“Get it now” button disabled or blocked

  • Symptoms: AppSource page shows disabled purchase/install controls.

  • Causes:

    • User lacks tenant permissions.

    • Marketplace purchases disabled by policy.

    • Conditional Access blocking flow.

  • Resolution:

    • Ask a Global Admin or Power Platform Admin to perform installation.

    • Request exception or temporary enablement of marketplace acquisition.

    • Complete MFA/CA prompts and retry.

No eligible environments shown

  • Symptoms: During AppSource flow, the environment list is empty.

  • Causes:

    • No environments where user is admin.

    • Environments lack Dataverse or D365 apps enablement.

  • Resolution:

    • Verify role assignment and environment permissions.

    • Provision Dataverse in the target environment and enable Dynamics 365 apps, then retry.

Installation stuck at “Installing”

  • Symptoms: Solution remains Installing > 60 minutes.

  • Causes:

    • Dependent solution install latency.

    • Capacity constraints or service incident.

  • Resolution:

    • Check Power Platform admin center → Health for incidents.

    • Review Solutions → History for failure messages.

    • If failed, retry install; otherwise open a Microsoft support ticket and include correlation IDs.

Missing or invalid connection references

  • Symptoms: Flows are off or immediately fail; error mentions connection reference.

  • Resolution:

    • Open the CT REx solution → Connection references → set or fix each one.

    • Turn on all flows and re-test.

Insufficient privileges / access denied for users

  • Symptoms: Users can’t see CT REx app areas or receive access errors.

  • Resolution:

    • Confirm users have Dynamics 365 Sales license.

    • Assign appropriate CT REx security role(s).

    • Publish the CT REx app to those roles.

App not visible in the Apps list

  • Symptoms: CT REx app not listed under Apps.

  • Resolution:

    • Verify solution installed successfully.

    • Confirm the app was Published and Shared to relevant security roles.

Environment variable or configuration errors

  • Symptoms: Features fail at runtime referencing missing configuration.

  • Resolution:

    • Review Environment variables in the CT REx solution.

    • Provide correct values per environment and Publish all customizations.

Dataverse capacity or API limits

  • Symptoms: Imports fail with capacity errors; throttling in automations.

  • Resolution:

    • Check capacity in Power Platform admin center.

    • Increase capacity or optimize flow schedules/retries.

Security & Compliance checklist

  • Verify least-privilege assignment for CT REx roles.

  • Confirm data residency and retention align with your org’s policies.

  • Review audit and logging for CT REx custom tables/flows.

  • Document environment variable values and secrets ownership (use secure stores; rotate credentials as needed).

Operational best practices

  • Maintain aligned versions across Dev/Test/Prod.

  • Use Solution Packager and ALM pipelines for consistent deployments.

  • Keep a runbook with install/upgrade/rollback steps and validation checks.

  • After upgrades, re-run smoke tests for key CT REx scenarios.

Appendix: Quick verification steps (Sandbox)

  1. Admin opens Solutions → CT REx = Installed.

  2. All Connection references = Connected.

  3. All required Environment variables populated.

  4. App = Published and shared to roles.

  5. Flows = On and no recent failures.

  6. Test user with CT REx User role can access targeted app area and perform one end-to-end scenario.

Support

  • For installation or configuration issues, contact your internal admin team first.

  • If the problem persists, open a support ticket with:

    • Environment name and region

    • Solution version

    • Time of failure and correlation ID (if available)

    • Screenshots of Solutions status, connection references, and error details

``