-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added a file dialog in order to select an Excel template file #2
Comments
Thanks for the contribution! I would keep it on hold for a future release, the priority is now fixing issues that are appearing when the configuration is not good (missing Excel, missing OLAP drivers, ...). |
@didierterrien I have a question - when you open an existing file with your code, do you change the connection string? It doesn't seem you do that, but maybe I'm missing something. |
Hello @marcosqlbi,
|
Thanks for the explanation! |
Hello Marco, Do you agree if I reuse a part of your code (ODC_Helper) in my external tool ? Of course I will add credits to you. https://thebipower.fr/index.php/power-bi-sidetools/ Best regards |
No problems, it is allowed by the MIT license, I suggest you check it because it has an impact on the license of your tool. |
Thanks a lot Marco, |
Great - thanks! |
Hello Marco,
I tried to submit a pull request but I couldn't succeed. So I add the new version of RunExcelProcess down below.
I added a file dialog in order to select an Excel template file.
If cancel button is pressed, an empty file is open (previous behaviour).
The template file can be created from an empty file. Open connection properties and check these 2 options :
When the template is open from external tools, data is refreshed automatically without any message.
Thanks again for this fantastic tool
Didier Terrien
`
private void RunExcelProcess(string serverName, string databaseName, string cubeName)
{
// Create ODC file
OdcHelper.CreateOdcFile(serverName, databaseName, cubeName);
var ODCfileName = OdcHelper.OdcFilePath();
`
The text was updated successfully, but these errors were encountered: