Hi @SharePointAdmin1030
Issue with Power BI Slicer Date Format: To address the problem with the Power BI slicer date format showing as mm/dd/yyyy instead of the desired dd/mm/yyyy format when embedded on SharePoint, you can try the following steps:
Check SharePoint Regional Settings: Double-check that the regional settings on the SharePoint site are indeed set to English (U.K.). This can be done by going to Site Settings > Site Administration > Regional settings and confirming the locale is set to United Kingdom.
Check SharePoint Site Collection Settings: Ensure that the regional settings are consistent at the site collection level as well. Go to Site Settings > Site Collection Administration > Site collection features, and make sure that the feature "SharePoint Server Publishing Infrastructure" is activated.
Verify Browser Settings: Confirm that the browser you are using to access SharePoint has its language settings set to English (U.K.).
Check Date Format in SharePoint Lists/Libraries: Ensure that any SharePoint lists or libraries where the Power BI reports are being displayed also have their date format set to dd/mm/yyyy.
Clear Browser Cache: Sometimes, cached data can cause display issues. Try clearing your browser's cache and reload the SharePoint page containing the embedded Power BI report.
Reach Out to SharePoint Support: If the issue persists after trying the above steps, you can contact Microsoft SharePoint Support to seek further assistance. To contact SharePoint Support, follow these steps:
a. Go to the Microsoft 365 admin center: https://admin.microsoft.com/ b. In the left-hand menu, select "Support" > "New service request." c. Choose "SharePoint" as the product and select the appropriate issue category (e.g., "Report and Dashboard Issues"). d. Follow the prompts to describe the issue and submit your request.
Regarding Sharepoint Migration Tool:
Unfortunately, if the SharePoint Migration Tool has already been updated, and you no longer have access to the old migration configurations, it may not be possible to retrieve them without restarting the whole migration process. When the tool updates, it may not be compatible with the old configurations, and using a different server might not help in this case.
To avoid losing your migration progress, it is recommended to take a backup of your existing migration configurations before any updates or changes are made to the migration tool. Additionally, consider contacting Microsoft Support to see if they can provide any guidance or assistance regarding the migration tool and your specific scenario.
Remember, always proceed with caution when dealing with migration processes and consider taking backups or snapshots to ensure data integrity and minimize potential data loss.
