web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Absolute URLs detected...
Customer experience | Sales, Customer Insights,...
Suggested answer

Absolute URLs detected during SharePoint upgrade (2016 on-prem)

(0) ShareShare
ReportReport
Posted on by DorienM 30

Hey All, I am currently running 2016 on prem and we are upgrading our sharepoint server from 2007 to SharePoint Online. The documents have been moved, all thats left is to change the integration in CRM to server based.

I have updated every single document location (~1800 of them) from an absolute URL to a relative one. The trouble here is when I open the server based integration wizard I get the absolute URLs detected message. I checked my document locations and filtered for absolute URL contains data and got no results back. There isn't a single document location with an absolute URL left.

I am thinking this is being triggered because the parent sites are absolute URLs but there is no choice here the top level sharepoint sites need to be absolute URLs. I can't remove these without taking out hundreds of child records.

Is anyone able to assist here?

I have the same question (0)
  • ChrisPiasecki Profile Picture
    ChrisPiasecki 4 on at
    RE: Absolute URLs detected during SharePoint upgrade (2016 on-prem)

    Hi ,

    The Site records can be an absolute url and should be since that represents the top level site. Have you tried searching via Advanced Find for all Document Location records that have an absolute url? Perhaps there were some records marked as Inactive that were filtered out of your original search.

    Here's more detail on configuring the server based integration. 

    https://support.microsoft.com/en-us/topic/-validation-error-when-you-try-to-configure-server-based-sharepoint-integration-for-microsoft-dynamics-crm-online-and-sharepoint-online-c7ebbf1d-5b4d-b43d-8bfc-c00b1ee086b3

  • DorienM Profile Picture
    DorienM 30 on at
    RE: Absolute URLs detected during SharePoint upgrade (2016 on-prem)

    Yes, I am completely certain that ALL document locations are now relative. I changed them over to relative using an import rather than doing them all by hand as there are almost 1800 of them and it would take an insane amount of time.

  • ChrisPiasecki Profile Picture
    ChrisPiasecki 4 on at
    RE: Absolute URLs detected during SharePoint upgrade (2016 on-prem)

    Can you confirm that the Absolute Url field is actually empty with no white spaces on the DocumentLocatiom records? Try an export and check. CRM will trim white space on retrieve and will not show up in a Contains Data filter, yet may still have a white space in the underlying column in the database.

  • Suggested answer
    DorienM Profile Picture
    DorienM 30 on at
    RE: Absolute URLs detected during SharePoint upgrade (2016 on-prem)

    I want to emphasize just how certain I am that each and every one of those fields is blank. There is not a single character existing in any row under the absolute url column. I have verified this with filters, with advanced find, and with SQL queries.

    That said I decided to cut my losses and delete each document location. I have an export of them all and will just reimport them once I am done.

    For anyone else that comes across this post in the future. If you have this issue and you are absolutely 100% certain they are all relative URLs save yourself some time, export the document locations and resolve the regarding column to GUIDs so you can reimport them later.

  • Nefeli Profile Picture
    Nefeli 5 on at
    RE: Absolute URLs detected during SharePoint upgrade (2016 on-prem)

    Hello,

    I am having the same issue. Did you manage to solve it?

  • CU24121345-0 Profile Picture
    CU24121345-0 2 on at
    Absolute URLs detected during SharePoint upgrade (2016 on-prem)
    Run the below SQL 

    SELECT COUNT(*)
    FROM SharePointDocumentLocationBase
    WHERE SiteCollectionId IS NULL;
     
    These are the problem record , as SiteCollectionId should not be null .
     
    Below query should fix it 

    update SharePointDocumentLocationBase
    set SiteCollectionId = '2D38ACC5-E707-E211-ABDB-000C299CC541' --- copied from other records
    where SiteCollectionId IS NULL;
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Rishabh Kanaskar Profile Picture

Rishabh Kanaskar 149

#2
MVP-Daniyal Khaleel Profile Picture

MVP-Daniyal Khaleel 132

#3
Tom_Gioielli Profile Picture

Tom_Gioielli 123 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans