Finance | Project Operations, Human Resources, ...

Error while opening Data entity template using excel add-in

(0) Share

Report

Posted on by nithinkumar_007

152

Hi All,

When some users are trying to open the data entity template through excel add-in, they are getting the following error:

7230.entity.png

An Error occurred while retrieving the row count of entity VendorInvoiceHeader.

Error Details: The query may contain too many parameters. Please reduce the number of parameters and try again.

Could anyone help on this issue.

Thanks,

Nithin.

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

Ramit Paul 22,805 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi,

What exactly you are trying? Are you adding too many fields from design?

Was this reply helpful? Yes No
nithinkumar_007 152 on at

Like (0)

Report
Copy link

Link copied!

Hi Ramit,

When using system administrator it is working fine. But for some user user without the system admin it is showing the error.

Thanks

Nithin

Was this reply helpful? Yes No
Vinod Kumar Reddy 285 on at

Like (0)

Report
Copy link

Link copied!

Hi guys,

Anyone have solution to this issue. even we are facing same issue.

Was this reply helpful? Yes No
Suggested answer

Ramit Paul 22,805 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi Vinod,

Have you checked if the user has office integration power user assigned under system user?

it seems an access issue.

Was this reply helpful? Yes No
Clive Richard Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hello All,

This might be an old thread however there are still instances where the issue occurs while using the excel add-in so wanted to share the observations found by one of the client-side users who was kind to share the details.

you will need to start with investigating if the metadata of the entity has lot of fields and navigation property which might be a reason for the SQL query having too many parameters.

If the above is not the case, as the end user (who helped in resolving the issue) solved the issue by reimporting a specific user again into D365FO which resolved the issue, this is worth trying if all the users who are not system admin has the same issue.

Please note: Above summary is based on my observations and my own opinion, DOES NOT make an official statement from my organization or Microsoft.

Was this reply helpful? Yes No