Hello Marco,
Testing V1.1.1 I notice Excel shows the dialog box in order to approve opening the ODC file. I double checked I use version 1.1.1. I checked also the connection which is actually made with the ODC file.
I deleted the ODC file but it was created again by your tool so I'm sure COM Interop failed.
Please let me know if you need more information
Thanks in advance
Didier Terrien

I had Power BI 64 with latest version of this program and it works
I need to uninstall Power BI 64 in spite of 32 and the program stopped to work.
The issue was not solved also reinstalling the program in older version or passing from Office 2019 to 365
Luca

Hi install this tools on two machines. One is working perfectly, my personal laptop. On my company laptop, I receive this message without Excel open, "Excel is not available. Please check wether Excel is correctly installed". Excel Office 265 ProPlus 64-bit english version. I'm administrator on both machine.

How I can resolve this issue?

Thanks and good work!

Frédéric

If Power BI has no data or is connected to an external dataset (report only mode), then launching Excel is useless because it will raise an error.
We could detect this condition before launching Excel, assuming that the check can be quick enough to not increase latency starting Excel.

Hi Marco, great idea, I am used to to this same technique but manually, finding out the SSAS Tabular port.
The button is grayed out.
I installed using the MSI you posted in the previous issue.
Mariano

If the model has perspectives, it would be a good idea to show a dialog box to select the desired Perspective before opening Excel.

I have not been able to add any numerical field to the Values area of the newly created pivot table. I've checked that in Power BI the field is a formatted

Windows 10 Pro x64 Build 19041.450, Excel Pro Plus 2019 x64 Build 13127.20208, Power BI Desktop x64 July 2020 Ver 2.83.5894.961, x64_15.0.2000.475_SQL_AS_OLEDB

CUBEVALUE Excel function does not work if I use Analyze in Excel extension.
But if I go thought Dax Studio, and then use the advanced tab > Excel, it works.

PBI version 2.86.727.0 64-bit
Excel version 16.0.13231.20372 64-bit

PBISampleCubevalue.zip

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 :

• in first tab : refresh data when the file is open
• in second tab : always use the connection file

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();

        // Select an Excel template. If Cancel button is pressed, an empty Excel file is opened
        string selectedFileName = "";
        OpenFileDialog openFileDialog = new OpenFileDialog
        {
            Title = "Select an Excel template file",
            //InitialDirectory = Directory.GetParent(Power_BI_file).ToString(),     //would be nice to start searching from the Power BI file folder
            Filter = "xlsx files (*.xlsx)|*.xlsx|xlsm files (*.xlsm)|*.xlsm|All files (*.*)|*.*",
            FilterIndex = 2,
            Multiselect = false,
            RestoreDirectory = true
        };
        if (openFileDialog.ShowDialog() == true)
        {
            // If ok is pressed, get the path of selected file
            selectedFileName = openFileDialog.FileName;
        }
        else
        {
            // If Cancel is pressed, use the ODC file
            selectedFileName = ODCfileName;
        }

        var p = new Process
        {
            StartInfo = new ProcessStartInfo(selectedFileName)
            {
                UseShellExecute = true
            }
        };
        p.Start();
    }

`