Customer experience | Sales, Customer Insights,...

Siteurl cannot be null or emtpy

(0) Share

Report

Posted on by Erik KOhler

414

Hello all,

my colleague wants to add documents to a sales opportunity, saving these on the corresponding Sharepoint site. She always runs into the following error.

Siteurl cannot be null or empty. Please ensure valid Sharepoint site is configured or contact your administrator.

Errorcode: 0x80060768

However, the Sharepoint site exists, I can drop doucments without a problem, another colleague can do it, too. The colleague with the error has full rights on the Sharepoint site and the same D365 Sales permissions as I do.

Anyone got a clue, what the problem might be?

Cheers,

Erik

All responses (4)

Answers (0)

Community member 4 on at

Like (1)

Report

Siteurl cannot be null or emtpy

A user has kept getting this when trying to upload documents. As previous answers suggested I validated the site URL (didn't help) then start comparing security roles and turned out one of the role user had doesn't have the privilege to access SharePoint Site but another role has had 'read' and 'append to' rights
Community member 2 on at

Like (0)

Report

Siteurl cannot be null or emtpy

I had the same issue, below one resolved mine.
Suggested answer

Community Member Microsoft Employee on at

Like (0)

Report
RE: Siteurl cannot be null or emtpy

Hi Erik,

1.Compare the security roles held by two users.

2.Let colleague upload many documents or you try to upload same document from the colleague.

3.Try to upload documents in other entities.

4.Go to the Power Apps, Opportunity Main Form, and changed the configurations of the Documents Sub-grid.

Table: Documents(Regarding)

View: All SharePoint Documents

5.Re-ran the document management wizard on Opportunity entity.

6.Open one ticket for Microsoft Support:

admin.powerplatform.microsoft.com/support
Mahendar Pal 45,095 on at

Like (0)

Report

RE: Siteurl cannot be null or emtpy

Hi Erik,

You can try some possible options

> Provide this user System Admin right for testing and see if still facing same issue, if not it could be related to the permission issue somehow.

> Another option is to clean browser cache or try with different browser and see if still facing same issue

> You can also start developer tool in the browser and check if there is anything reported in the console.