Forum Discussion
Helper IVUpdating existing SharePoint Connection to V2
Good day to all,
Is there an easy way to convert from an older V1 connection to the V2 without having to reset all of the subsequent steps?
The V1 is incredibly slow and we need a faster refresh solution.
I tried modifying the original to match the new string ([Implementation="2.0", ViewMode="All"])) through the Transform but it errors out.
Please note that I have found this: https://community.powerbi.com/t5/Desktop/SharePoint-list-query-alternative-or-optimization/m-p/1092677
However, it does not cover a conversion but new connections as far as I can tell. (I also followed the other links and Vids from there with the same observation.)
Anyone have a valid solution that would save me many hours of work to reset and match the existing connection/steps?
Thanks,
Trent
I assume v1 and v2 are returning different columns, so you are getting downstream errors. Instead of rebuilding your queries, you can do the following:
- make a new query with the v2 connector
- do any steps to get the data looking just like one of the steps in your original query
- copy the new steps from the Advanced Editor and paste them over the first steps of your existing query (updating any references between steps)
- Delete the new query you copied the new M code from.
With this approach, it is the original query that is still loading, and you won't have to re-make your relationships either.
Pat
2 Replies
- mahoneypat
Microsoft Employee
I assume v1 and v2 are returning different columns, so you are getting downstream errors. Instead of rebuilding your queries, you can do the following:
- make a new query with the v2 connector
- do any steps to get the data looking just like one of the steps in your original query
- copy the new steps from the Advanced Editor and paste them over the first steps of your existing query (updating any references between steps)
- Delete the new query you copied the new M code from.
With this approach, it is the original query that is still loading, and you won't have to re-make your relationships either.
Pat
TrentSmahoneypat Thank you.
I will try out that method. I did discover a couple of other items that could be affecting the refresh but I certainly want to update the connection. As you suspected, some column information is mismatching now,
so there is some effort there in the schema.Thanks again,
Trent