Sharepoint Documents "Something went wrong"

(0) Share

Report

Posted on by Steve123

Hi,

I've been having this issue for a few days and can't figure a way around it.

On the customer side, I'm using a basic form, set to read only, to show data on opportunities. This form can show other data fine, just the documents section shows a message saying "We're sorry, but something went wrong. Please try again, and if this persists, contact the website administrator." in a red box. I thought it would be a permissions error, however if I play with the permissions, I'll get a different error saying something along the lines of you don't have the appropriate permissions.

There's also a 500 internal server error in the dev tools console log, which only appears when the documents section is being used on a page.

Further info:

The opportunityid is being passed in through the url params, this works fine and can get the data for other sections fine.

I'm able to get information such as document names through a view on a different page, so I really don't think it's a permissions problem.

I've been stuck for days, this is doing my head in, it's the last thing that really needs doing for the website.

Categories:

Power Apps portals

error_message.jpg

I have the same question (0)

All responses (5)

Answers (1)

ragavanrajan 7,044 Most Valuable Professional on at

Like (0)

Report

Hi @Steve123

Need more info on this. What kind of document storage you are using? Is it a SharePoint file attachment or Azure blob storage attachment or notes attachment?

Did you give permission to the Annotation entity? please post the screenshot

Hope it helps.
------------

If you like this post, give it a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

Was this reply helpful? Yes No
Steve123 11 on at

Like (0)

Report

Hi Ragavanrajan,

This is a sharepoint attachment. I've followed all the steps in here, https://docs.microsoft.com/en-us/powerapps/maker/portals/manage-sharepoint-documents. All documents work fine on the admin side, just not the customer side.

What exactly do you mean by the annotation entity?

Thanks,

Steve

Was this reply helpful? Yes No
Steve123 11 on at

Like (0)

Report

So I've tried giving permission to the note/annotation entity, and I've tried adding this as a child permission to the Opportunities entity as well, neither made a difference.

Was this reply helpful? Yes No
Verified answer

AaronKGumbs 94 on at

Like (2)

Report

Check to see if the sub-grid renders correctly via the Dataverse Form configuration and from an end user's perspective using a model-driven app. I had this recently where the incorrect Document Location table was being referenced and with a little help from Microsoft Support we found out that this was due to an update that had taken place out of our control, and the best way to resolve it was by re-creating the sub-grid with the new Table reference added in the update.

Was this reply helpful? Yes No
Steve123 11 on at

Like (1)

Report

Thanks @AaronKGumbs ,

Switching the table referenced seems to have worked. Thanks!

Was this reply helpful? Yes No