---
title: "D365 Power Apps Solution Package Import and Sales Hub configuration"
slug: "d365-power-apps-solution-package-installation-integration-guide"
updated: 2026-08-27T05:58:18Z
published: 2026-08-27T05:58:18Z
canonical: "docs.saasify.ai/d365-power-apps-solution-package-installation-integration-guide"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.saasify.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# D365 Power Apps Solution Package Import and Sales Hub configuration

## In this Article

[Purpose and outcomes](/v1/docs/d365-power-apps-solution-package-installation-integration-guide#purpose-outcomes)

[1. Roles and prerequisites](/v1/docs/d365-power-apps-solution-package-installation-integration-guide#1-roles-and-prerequisites)

[2. Import the monthly solution package](/v1/docs/d365-power-apps-solution-package-installation-integration-guide#2-import-the-monthly-solution-package)

[3. Configure the environment](/v1/docs/d365-power-apps-solution-package-installation-integration-guide#3-configure-the-environment)

[4. Configure the Sales Hub app](/v1/docs/d365-power-apps-solution-package-installation-integration-guide#4-configure-the-sales-hub-app)

[5. Integration via SaaSify](/v1/docs/d365-power-apps-solution-package-installation-integration-guide#5-integration-via-saasify)

[6. Troubleshooting and escalation](/v1/docs/d365-power-apps-solution-package-installation-integration-guide#6-troubleshooting-and-escalation)

### Purpose and outcomes

> **Purpose:** Provide a repeatable process for importing the monthly D365/Power Apps solution package, applying CSM-provided environment-variable values, and exposing the Co-sell Dataverse table in the Sales Hub app.

| **Process owner** | Application Administrator / Deployment Engineer |
| --- | --- |
| **Package cadence** | Monthly — developer provides a new solution package |
| **Required input** | Environment-variable values supplied by the CSM team |
| **Target portal** | https://make.powerapps.com |

Outcome: The solution imports successfully into the intended Power Platform environment; the Sales Hub app contains a new group named SaaSify, and the Co-sell page is published and available when the app is played.

### 1. Roles and prerequisites

| Developer | Provide the newly managed solution package each month. | Current package file and version/release identifier. |
| --- | --- | --- |
| CSM team | Provide the environment-variable values for the target customer/environment. | Confirm current values for every prompted variable. |

**Pre-deployment checklist**

☐ Confirm the target customer and Power Platform environment name.

☐ Confirm the package is the current monthly release and is stored as a supported solution .zip file.

☐ Obtain all environment-variable values from the CSM team.

☐ Confirm there is no conflicting deployment already running in the target environment.

☐ Plan for at least 10 minutes of unattended import time, plus validation time.

> **Control point: Never** guess environment-variable values. Kindly confirm from your SaaSify Customer Support team before completing the import.

### 2. Import the monthly solution package

**Note:** For monthly package updates, only the solution import and environment-variable update steps are required. The remaining Sales Hub configuration steps apply only when onboarding a new customer.

#### **STEP 1 |** **Open the Power Apps maker portal**

Go to https://make.powerapps.com and sign in with the authorized deployment account.

Use the environment selector in the upper-right area to choose the intended target environment.

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809284271.png)

**Verification:** The target environment name shown in the portal matches the deployment request.

#### **STEP 2 |** **Start the solution import**

In the left navigation, select Solutions.

Select the Import solution, then browse and select the new monthly solution package provided by the developer.

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809284277.png)

Select Next and review the package details before continuing.

For package updates: under **Solution Action,** choose Stage for Stage Upgrade.

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809284279.png)

**Verification:** The package name and version match the current monthly release.

#### **STEP 3 |** **Enter environment-variable values**

On the environment-variable configuration screen, enter the values supplied by the CSM team.

Review each name and value carefully, then continue with the import.

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809284282.png)

**Important:** Do not substitute values from another customer or environment unless the CSM team explicitly confirms them.

**Verification:** Every required environment variable has a confirmed value.

#### **STEP 4 |** **Wait for the import to finish**

Start the import and allow approximately 5–10 minutes for the solution to upload and install.

Keep the portal open and monitor the import notification or solution status.

**Verification:** The portal reports that the solution import was completed successfully. If it fails, capture the error details and do not proceed to app configuration.

### 3. Configure the environment

#### **STEP 5 |** **Increase file attachment size**

From the header, select the environment name.

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809285146.png)

Hover over the selected environment, select **See details,** then select Go to **the admin center.**

This opens the admin center. Select Settings.

Once Settings open, select **Email settings.**

Update the attachment file size limit to **131072.**

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809285302.png)![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809285393.png)![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809285456.png)

#### **STEP 6 |** **Add application user**

On the Settings page, under **Users + permissions, select Application users.**

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809286025.png)

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809286379.png)

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809286481.png)

Select Add an app. In the search box, search for ![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809286537.png) **SaaSify - Private offer and Co-sell automation platform for Cloud Marketplaces** and choose it.

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809286990.png)

Business unit: choose the suggested unit.

Security role: click the edit icon, search for SaaSify Admin User, and add it.

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809287187.png)

### 4. Configure the Sales Hub app

#### **STEP 7 |** **Open Sales Hub in the app designer**

From the left navigation, select Apps.

Select All to display all available apps.

Locate Sales Hub, open its More commands menu, and select Edit.

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809287326.png)

**Verification:** The Sales Hub app opens in the app designer.

#### **STEP 8 |** **Create the SaaSify group**

In the app navigation editor, locate and hover over the Sales group.

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809287414.png)

Select New group.

Enter SaaSify as the group name.

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809287735.png)

**Verification:** A group labeled SaaSify appears in the Sales Hub navigation.

#### **STEP 9 |** **Add the Co-sell Dataverse table**

Within the SaaSify group, select New Page

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809288159.png)

Choose Dataverse table as the page type.

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809288234.png)

Search for Co-sell, select the matching table, and add it to the app.

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809288302.png)

> **Important:** If more than one similarly named table appears, confirm the correct table with the solution owner before selecting it.

**Verification:** The Co-sell page is listed under the SaaSify group.

#### **STEP 10 |** **Publish and test**

Save the app changes.

Select Publish and wait for the publish operation to complete.

Select Play to open the updated Sales Hub app.

**Verification:** In the running app, the SaaSify group is visible, and its Co-sell page opens successfully.

### 5. Integration via SaaSify

#### **STEP 11 |** **Open SaaSify web portal**

Navigate to the Power Apps admin center to get the Account URL and Organization ID.

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809288631.png)

On the SaaSify web portal, navigate to the Integrations section, enter the Account URL and Organization URL, then save and validate.

![](https://cdn.document360.io/ee554fce-9bf4-4a4c-9d38-d2096a575aab/Images/Documentation/base64-converted-image-1787809288959.png)

### 6. Troubleshooting and escalation

- **Import remains in progress:** Wait a few more minutes and refresh the Solutions view. Do not start a duplicate import while the first job may still be running.
- **Import fails:** Capture the error message, timestamp, environment, solution name/version, and any downloadable log. Send these details to the developer or solution owner.
- **Environment variable is missing:** Pause the deployment and request the correct value from the CSM team.
- **Sales Hub cannot be edited or published:** Confirm the deployment account has the required maker and app customization permissions in the selected environment.
- **Co-sell table is not available:** Confirm that the solution import succeeded and that the expected table is included in the imported package.

> **Final acceptance: Deployment** is complete only after the solution shows a successful import status, and the published Sales Hub app displays SaaSify → Co-sell without an access or loading error.