Error on Connecting at Sharepoint list

(0) Share

Report

Posted on by Community Power Pla...

When I try to connect to a sharepoint list, I'm getting this error:

"status": 400, "message": "Specified argument was out of the range of valid values.\r\nParameter name: DisplayName",

It occurs only with one list.

I have Full-Permission.

It is the same with different accounts.

Categories:

Using connectors

I have the same question (0)

All responses (5)

Answers (1)

v-yamao-msft on at

Like (0)

Report

Hi Piagno,

I guess that it might relate to your SharePoint list configurations.
Do you have any special configurations on the list?

Best regards,
Mabel Mao

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

There is a setting called "Project Server-Settings".
I don't know if it is new (since the flow doesn't work) or if it appeared since I got the "Project"-License.
It is beeing synchronised with a local "Navision" table. This shouldn't be a problem, because it is only syncing upwards to sharepoint.

I don't see any other changes or special configuration in this list.

Was this reply helpful? Yes No
Verified answer

Community Power Pla... on at

Like (0)

Report

I actually had to delete the invalid column "DisplayName".
I tried to create another column called "DisplayName" as a calculated column.
But Flow somehow didn't accept a column "DisplayName".
Then I created the same calculated column as "FullName" and it worked.

Was this reply helpful? Yes No
kelin 2 on at

Like (0)

Report

At first, I'm trying to create a form using powerapps. After that, I wonder where the data will be kept and I discover SharePoint. I try to connect the data source with SharePoint using power apps, however, it shows using these connections will conflict with the company data loss prevention policies. I would like to ask how to solve this problem. '

Was this reply helpful? Yes No
PiagnoF 24 on at

Like (0)

Report

You should probably talk to an sysadmin of your company, since the data loss prevention policy was configured by someone in your company.

Was this reply helpful? Yes No