Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi
When trying to import an SP from SQL Server, I get a message stating that
"The data source appears to have been modified since it was last accessed. Refreshing may resolve this error."
The query I am trying to load is almost exactly the same as the one I loaded before it, only referencing a different table in SQL Server. The only other thing of note is that I have, for this particular table, to resolve an error about a collation conflict between SQL_Latin1_General_CP1_CI_AS and Latin1_General_CI_AS, which I have to run the below for all 3 columns in the table concerned.
Anyone have any ideas? I should add it's in Import mode, run as an advanced query which just calls the SP name and @ variable that goes with it.
ALTER TABLE YourTableName ALTER COLUMN OffendingColumn VARCHAR(100) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL
Solved! Go to Solution.
In the end, I copied the relevant parts of the SP I needed to keep, then created a new one from an existing SP template, swapping out the main code. I called it something slightly different, and this time it worked a treat.
Maybe I created the SP already at some point either by accident, or not recalling, and this was why. Either way, renaming the SP and adding it again seems to clear this particular issue.
You might be faster off deleting the data source and recreating it.
One word of caution: DAX is not case sensitive. It will ignore your collation settings.
Hi @Anonymous ,
Please review the solution in the following threads and check whether it can resolve your problem.
New Error When Getting Data From SQL Database in Excel
Can't import Azure SQL View into Excel
Best Regards
Rena
Hi @Anonymous ,
Did you try to click "Refresh" button? If no, could you please refresh the report and check if it still got that error message?
Best Regards
Rena
In the end, I copied the relevant parts of the SP I needed to keep, then created a new one from an existing SP template, swapping out the main code. I called it something slightly different, and this time it worked a treat.
Maybe I created the SP already at some point either by accident, or not recalling, and this was why. Either way, renaming the SP and adding it again seems to clear this particular issue.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
113 | |
97 | |
85 | |
70 | |
61 |
User | Count |
---|---|
151 | |
121 | |
104 | |
87 | |
67 |