Copyright ©LowCodeGo 2025
For additional support, please contact us at:
solutions@lowcodego.com
Go to https://make.powerapps.com.
Sign in with your Dynamics 365 / Power Platform credentials.
In the top-right corner, confirm you are in the environment where you want to import the solution.
If not, use the environment picker to switch.
From the left-hand menu, select Solutions.
On the command bar, click Import solution.
Browse and select your .zip file (the managed solution package).
Click Next.
Confirm the solution name, publisher, version, and type (Managed should be displayed).
Click Next.
Enter the license key provided with the solution for the target environment.
If the license key is not available, click Next. You can update the variable later.
Click Import.
The process may take several minutes depending on solution size and complexity.
Once complete, you’ll see a confirmation message.
If any issues occur, review the Import log for details.
Open Solutions
Go to https://make.powerapps.com.
Select the correct environment.
In the left menu, choose Solutions.
Check the Top Ribbon
If the solution requires a value for an environment variable (e.g., a license key), you’ll see a yellow notification bar at the top that says:
“Enter a value for environment variable(s).”
Enter the License Key
Click the Edit environment variables option in the ribbon.
Locate the variable for the license key.
Paste or type in the value provided.
Create or Use an Unmanaged Solution
In Solutions, either open an existing unmanaged solution or create a new one.
Add the Environment Variable
Click Add existing → More → Environment variable.
Locate and select the environment variable for the license key that was created with your managed solution - lcgsltn_AuditViewerLicense.
Click Add.
Edit the Environment Variable
Open the environment variable component you just added.
In the Current Value field, enter the license key.
Save
Save the changes.
To ensure users can properly access and use the solution features, you must assign the correct security permissions. There are two ways to handle this:
The solution includes a pre-configured role named LCG – Audit Viewer User.
Assign this role directly to any users who need access.
This is the recommended option, as it’s the quickest and ensures all required permissions are applied.
If you prefer to use an existing security role that your users already have assigned, update it with the following permissions:
Environment Variable Definition → Read → Organization level
View Audit History → Organization level
View Audit Summary → Organization level
Updating an existing role may be useful if you want to maintain fewer roles in your environment or align permissions with your organization’s existing security model.
To ensure users can properly access and use the solution features, you must assign the correct security permissions. There are two ways to handle this:
The solution includes a pre-configured role named LCG – Audit Viewer User.
Assign this role directly to any users who need access.
This is the recommended option, as it’s the quickest and ensures all required permissions are applied.
If you prefer to use an existing security role that your users already have assigned, update it with the following permissions:
Environment Variable Definition → Read → Organization level
View Audit History → Organization level
View Audit Summary → Organization level
Updating an existing role may be useful if you want to maintain fewer roles in your environment or align permissions with your organization’s existing security model.