Import solution - Unexpected : Array dimensions exceeded supported range.

(1) Share

Report

Posted on by pawan_vertas

Hi,

I am trying to import a solution from Dev env to PROD env getting below error -

Unexpected : Array dimensions exceeded supported range.

Same solution from Dev imported successfully in UAT, but getting issues in PROD.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (10)

Answers (1)

mlaines 2 on at

Like (0)

Report

This error occurs when the solution is very large, probably the components that you are going to deploy require space that you do not have available in your Tenant, I suggest that you check the current space.

Was this reply helpful? Yes No
pawan_vertas 10 on at

Like (0)

Report

Thanks, but as i can see there is enough space in tenant but still unable to import.

Was this reply helpful? Yes No
harrygraham 3 on at

Like (0)

Report

I am also receiving this error message and I have raised a ticket with Microsoft - they don't seem to have a solution as of yet but I will post here when they do. As for the solution being too large, my solution that I am importing is 152KB, whereas the maximum size for a solution is 32MB in size Solution concepts - Power Platform | Microsoft Learn.

Was this reply helpful? Yes No
Gusz 10 on at

Like (1)

Report

we are also facing this issue, has anyone found a fix?

Was this reply helpful? Yes No
vidyacollation 5 on at

Like (0)

Report

Even we are facing the same issue. But it was working earlier (last time we checked 3 months ago)

Was this reply helpful? Yes No
Nud Dude 15 on at

Like (0)

Report

Same issue here...

Was this reply helpful? Yes No
Gusz 10 on at

Like (0)

Report

we solved this by removing the following entities from our solution that were omnichannel related:
-Active ICD Extension
-Entity-Workstream Map
- ICD Extension

Was this reply helpful? Yes No
Verified answer

Nud Dude 15 on at

Like (0)

Report

Got the info that this is a Bug which will be addessed with an Update. For EMEA it is planned for the 23rd of Feb.

Workaround make sure all dependancies package solution version is the same on the source and target environment. You will find in the solution.xml fine something like this:

<MissingDependency>
<Required type="1" schemaName="adminsettingsentity" displayName="admin_settings_entity" solution="msdynce_SalesPatch (9.0.1904.3002)">
<package>msdynce_SalesAnchor (9.0.24012.10004)</package>
</Required>
<Dependent type="80" schemaName="new_Test" displayName=2024+" />
</MissingDependency>

This means all MS Applications (Admin Center) must have the same versions in both systems.

Was this reply helpful? Yes No
sharonsammy123 40 on at

Like (0)

Report

I am also getting this error, any update on when it will be fixed (in Australia).

UPDATE - I tried this the day after my post and there was no error - looks like the bug was fixed.

Was this reply helpful? Yes No
sharonsammy123 40 on at

Like (0)

Report

Update on this post - now working and I did not do anything different. Looks like it was a bug that has been fixed.

Was this reply helpful? Yes No