Using Sharepoint Document table in powerapps

(1) Share

Report

Posted on by Community Power Pla...

Hi all,

Having had a good look at this, what I want to do doesn't seem possible. My question is why is this the case?

Within Dataverse on a Dynamics instance there is a table called Sharepoint Document. This contains fields relating to the location and metadata of documents associated to another table (usually Incident for us) so that the document list in Sharepoint can be rendered in Dynamics. However, I am unable to use this data anywhere else: Powerautomate, advanced find, Docscorepack etc. can all see the table and fields, but can't return any data. This is annoying, and I wonder why it is so.

Any help gratefully received

Ralph

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (9)

Answers (0)

Mira Ghaly 11,413 Moderator on at

Like (1)

Report

@Anonymous

If you elaborate more what do you want to do with this data, we can work something out.

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

Like (1)

Report

@Mira_Ghaly
Thanks for the response:
So the specific thing here was that I wanted to use a Create or Update trigger on a filtered Sharepoint Document Table (contenttype eq 'x'), and then create a record in a custom Table that contained some other information and the Absolute URL for the Sharepoint document. For various reasons I can't use a Sharepoint trigger, and our existing HTTP triggered Flow is so cumbersome that it falls over frequently. I'm struggling to simplify the HTTP approach, and in theory this data is held within Dynamics/Dataverse and should be easily used (I can add the required fields to a view for example).

Hope that clarifies thing a bit...

Cheers
Ralph

Was this reply helpful? Yes No
ChrisPiasecki 6,422 Most Valuable Professional on at

Like (1)

Report

Hi @Anonymous,

There is a SharePoint Document Location table which contains a reference to the document libraries and folders in SharePoint tied to your D365/Dataverse table records. It does not store any data on the documents contained in those folders, therefore there is no Dataverse Power Automate trigger that you can leverage to know when a document was added. You'd have to leverage the SharePoint Power Automate connector for this.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No
Sunidhigambhir1 77 on at

Like (1)

Report

Hello,
sign in to PowerApps>>click on data icon>>add data>>select SharePoint site >>after that select name of your document table.
in that way we can add SharePoint Document table in PowerApps.

Was this reply helpful? Yes No
ansrikanth 329 on at

Like (1)

Report

MS retrieves the core document details in the run time, if that is what you are looking for. When you open the Related records -> documents, if you open your network monitor in developer tools, you will see a Fetch Query running, that is what the query that brings data from sharepoint (they must be using some sort of retrieve plugin on this table). That's the reason why you can't put any trigger on the actual document record it self. Unfortunately, I don't see any way for you to trigger the way you are thinking (when doc is created/updated).

I know you said it is not possible for you to use Sharepoint connector, but in my opinion that is the more appropriate and good design. you have to monitor for the file changes at your source (i.e Sharepoint).

Thank you
-Srikanth.

Was this reply helpful? Yes No
Len C 379 on at

Like (2)

Report

@Anonymous

What did you conclude on this? It looks to me like the table 'Sharepoint Document' is not actually used. It remains empty as documents are added.

Or, Dataverse has some magic to conceal the records from even system administrators.

It has a lot of fields I was envisioning needing for a custom solution. Would like to re-use if possible.

Was this reply helpful? Yes No
johnpgootee 16 on at

Like (4)

Report

Yes, this is quite annoying. My use case is that I want to trigger an esignature process on a document that is stored for my entity using SharePoint integration. I can write a Power Automate trigger using the dataverse(legacy) trigger for a selected record on the Document table and it will fire appropriately, but there is no data returned. The document table is empty as indicated in the previous post.

Yes, i can go to SharePoint and trigger the esignature...but that becomes a bunch of extra clicks for the end user. The experience is really degraded by having to shift the user from Power Apps over to Sharepoint to accomplish this.

Was this reply helpful? Yes No
Suggested answer

CU07081004-0 2 on at

Like (1)

Report

The SharePoint Documents table is a virtual table as called out by Microsoft here as known issue: Known issues with document management - Power Platform | Microsoft Learn

Forcing the user to navigate over to native SharePoint to run the Flow ruins the user experience. Further, I need the information for the dataverse entity (the email addresses to use to for sending for esignature) that are defined on the entity for which documents are being stored.

Please fix Microsoft! It will make the platform much better for working with SharePoint.

Was this reply helpful? Yes No
CA-24090038-0 2 on at

Like (1)

Report

Even the built in capability in the documents subgrid is broken because of this.

If I want to set up a flow like this:

Nothing that is in the sharepoint documents table gets passed to the manual input of the power automate, and if the input uses the related parent table, like tasks, the document subgrid flow menu doesn't have the flow in it.

{
"entity": {
"entity": {}
}
}

Useless in its current state.

Was this reply helpful? Yes No