Hello, I am running into an issue and I am not sure how to tackle it. 
I want the files to go into a folder structure like: Business Central/Sandbox_Attachments/Customers/[Customer name] (Customer No)/2025
I have the vendor and customer folders static with Business Central/Sandbox_Attachments/Customers as the folder, and the name and no. as the next part of the path and that works fine.
The next part for the document types, we do not need it separated by the type and instead want it seperated by the year which I have added a field Posting_Year that acts correctly in the file path.
This is the folder mapping that shows as the path in BC when I click the folder path button in the factbox:
This is the correct path I want the file to have. However when I drag a file into the sharepoint factbox I get this error:
Where its putting an extra “/” between the customer and the year.
The weird thing is its only some vendors and customers, ones that I tested with before getting the path correct and if I use other customers/vendors it goes through fine.. I had deleted the folders in sharepoint so that I didnt have a mess of things. I thought that might have been the cause so I took one of the working customers and deleted the folder, refreshed BC screen and uploaded just fine and created the folder again. I went back to the problem customer and it still throws the error.
Are you on the latest version of the SharePoint Connector, the double slash issue should be fixed?
But the year thing won’t work, because now you’re missing the identifier for the document in the URL now. We are working on an “Advanced Mapping Method” that will accomplish this. But probably not released until the fall.
Please keep me posted.
I believe I am, there is no update waiting in the admin panel I am running 6.0.0.4045
As for the URL, the URL works for uploading documents, in our case we do not want folders for each document we want all the documents in the same place to get multiple easily from sharepoint if/when asked. I get the double slash error on accounts that I was messing with the most when setting up the mappings I am thinking that the error wont be present when I put the extension in production but I could be wrong.