Forum Discussion
Helper IIIChanging data source from excel to SQL without losing calculated columns?
Hi qmartiny,
This is hard to say without having the actual model to play with, but I would doubt so. In my experience, this never happend. Not that I've done it million times, but quite a number of times.
Technically, losing of the calculated columns should not also occur in the normal way of business if the table name of the SQL version of the query is exactly the same as the old one (Excel-version of the query). The PBI is presumably agnostic of anything what happens on the query side and only deal with the output.
In the wort case scenario you could loose relationships and/or calculated columns. It should not really freeze the import. Would this be possible to verify your assumption to delete all the relationships to the table (in a copy of the model) and see if it loads Ok?
Could you please also check that not just the column names, but also the data types are the same as in the original table?
Good luck,
John
Memorable MemberHi qmartiny,
This is hard to say without having the actual model to play with, but I would doubt so. In my experience, this never happend. Not that I've done it million times, but quite a number of times.
Technically, losing of the calculated columns should not also occur in the normal way of business if the table name of the SQL version of the query is exactly the same as the old one (Excel-version of the query). The PBI is presumably agnostic of anything what happens on the query side and only deal with the output.
In the wort case scenario you could loose relationships and/or calculated columns. It should not really freeze the import. Would this be possible to verify your assumption to delete all the relationships to the table (in a copy of the model) and see if it loads Ok?
Could you please also check that not just the column names, but also the data types are the same as in the original table?
Good luck,
John
Helper IIIHi jbwtp
first of all thank you very much for your help so far.
As mentioned the new source has different columns + columns names.
As per your advice I made sure all where transformed to match the exact structure of the original table.
Yesterday I tried using an excel folder again to mimic the old query as close as possible but I still got the infinite loading.
Today I will attempt to clean up the existing relationships. The issue when I tried to do this yesterday is I had some calculated columns using "RELATED" that effectively froze the model if I removed the relationship without deleting the table..
happy days
Thanks again for your help.
i will let you know what happens
Quentin