98.7% Of all customers recommend us, we're so confident about our results we publish all reviews and stats
View Live Stats View ReviewsForum home » Delegate support and help forum » Microsoft Power BI training and help » Formatting Data from Sharepoint Folder
Formatting Data from Sharepoint Folder
Resolved · Low Priority · Version 365
Grant has attended:
Power BI DAX course
Power BI Reporting course
Formatting Data from Sharepoint Folder
I've noticed a difference in the data formatting when importing from a SharePoint folder vs importing from a local folder. I've built a report that combines multiple csv files to compare data over time. When I built it on my desktop it worked as intended, once I transferred the file and it's supporting data over to SharePoint so that my colleagues could interact with it the data started formatting differently.
When merging files and transforming the data using a local file PQ separates the columns using comma delimiters as one would expect. When opening the same files duplicated on a SharePoint folder PQ is splitting some of the data (presumably due to the presence of commas within the text) into rows instead, taking a single row of data and converting it to 57 rows.
RE: Formatting Data from Sharepoint Folder
Hi Grant
This is a common issue that can occur when working with CSV files in Power Query, especially when the data is being sourced from different locations like SharePoint and local folders. The issue you’re experiencing is likely due to how Power Query interprets the CSV files from SharePoint.
When Power Query reads a CSV file from a local folder, it uses the comma as a delimiter to separate the columns, which is the standard for CSV files. However, when the same file is read from a SharePoint folder, Power Query might interpret the data differently. This could be due to the way SharePoint handles and stores data, or it could be due to the presence of additional characters or formatting in the SharePoint version of the file.
Here are a few steps you can take to resolve this issue:
Check the CSV files on SharePoint: Open the CSV files directly from the SharePoint folder and check if there are any differences in the data or formatting compared to the local version of the files. Look for any additional characters or formatting that might be causing Power Query to interpret the data differently.
Specify the delimiter in Power Query: When importing the CSV files into Power Query, you can specify the delimiter that should be used to separate the columns. This can help ensure that Power Query interprets the data correctly, regardless of where it’s being sourced from.
Use Power Query’s ‘Clean’ function: Power Query has a ‘Clean’ function that can help remove any additional characters or formatting from your data. This can be particularly useful if the issue is being caused by additional characters or formatting in the SharePoint version of the files.
Re-upload the CSV files to SharePoint: If all else fails, you might want to try re-uploading the CSV files to SharePoint. It’s possible that something went wrong during the initial upload that’s causing the issue.
Let us know if your question remains after following those steps
Kind regards
Richard
STL - https://www.stl-training.co.uk
98%+ recommend us
London's leader with UK wide delivery in Microsoft Office training and management training to global brands, FTSE 100, SME's and the public sector
Welcome. Please choose your application (eg. Excel) and then post your question. Our Microsoft Qualified trainers will then respond within 24 hours (working days). Frequently Asked Questions
Any suggestions, questions or comments? Please post in the Improve the forum thread. |
Power BI tip:Stay Updated and Engage with the CommunityPower BI is continually evolving, with new features and updates being released regularly. Stay informed about the latest enhancements by regularly checking the Power BI blog and community forums. Engaging with the Power BI community provides opportunities to learn from others, share your experiences, and get insights into best practices. |