In September 2014, I wrote a weblog submit on dynamically passing parameters from PowerPivot to a SQL Server saved process utilizing VBA. Again then, VBA was an actual lifesaver. It maybe nonetheless is for many people. However frankly, I even forgot the right way to write VBA. Possibly it’s time to take a look at it once more. I additionally wrote a fast tip in August 2020 about doing a related factor in Energy BI utilizing Question Parameters. Test it out for those who’re eager to know the way it works in Energy BI.

Eight years later, one in every of my weblog readers requested the right way to do the identical factor in later variations of Excel; he’s particularly asking for Excel 2019. I assumed it might be good to cowl this matter after 8 years and see the way it works now. So, right here it’s, a brand new weblog submit.

The Downside

Sometimes, Excel customers require to get the information from a SQL Server saved process. The saved procedures normally settle for some enter parameters and return the outcomes. However how can we dynamically go values to the saved procedures from cells in Excel to SQL Server?

Stipulations

For this weblog submit, I exploit SQL Server 2019 and Microsoft’s well-known pattern database, AdventureWorks2019. You could find Microsoft’s different pattern databases right here. I additionally use Excel 365, it ought to work the identical approach in Excel 2019, although.

The Resolution

I focus on two approaches to beat the problem. Each approaches use Energy Question barely in a different way. In each approaches, we parameterise the SQL Assertion of the SQL Server connector, passing the values to the parameters from an Excel desk. One strategy requires ignoring the Privateness Ranges in Energy Question, whereas the opposite doesn’t. Each approaches work, however, relying in your preferences, it’s possible you’ll choose one over the opposite.

As talked about, I exploit the AdventureWorks2019 pattern database that comprises a few saved procedures. I exploit the dbo.uspGetBillOfMaterials saved process accepting two parameters, @StartProductID and @CheckDate.

Strategy 1: Parameterising the SQL connector’s SQL Statements, Ignoring Privateness Ranges

Observe these steps to go the parameters’ values from an Excel sheet to the saved process and get the leads to Excel:

1. In Excel, navigate to the Information tab
2. Click on the Get Information dropdown
3. Hover over the From Database possibility and click on the From SQL Server Database
4. Enter the Server
5. Enter the Database
6. Broaden the Superior choices
7. Sort EXEC [dbo].[uspGetBillOfMaterials] @StartProductID = 727, @CheckDate = N'2013-01-01' within the SQL assertion textbox
8. Click on OK

9. Click on the dropdown on the Load button
10. Click on Load to

From right here, we’ve some choices to load the outcomes both into an Excel sheet or the PowerPivot knowledge mannequin. We need to load the information into the PowerPivot knowledge mannequin on this instance.

11. Choose Solely Create Connection
12. Test the Add this knowledge to the Information Mannequin possibility
13. Click on OK

14. Rename the question to Invoice of Supplies
15. On the Rename Question warning, click on the Rename button

16. The thought is to go the parameters’ values from an Excel sheet, so I kind the next into the Sheet1:

17. Choose the vary we entered within the earlier step
18. Click on the From Desk/Vary from the Information tab
19. On the Create Desk window, be sure that the My desk has headers is ticked
20. Click on OK. This navigated us to the Energy Question Editor window

21. Rename the brand new question to Parameters

We now need to change the SQL Assertion of the Invoice of Supplies question to get the values from the related columns within the Parameters desk. Due to this fact, at any time when the consumer modifications the values on Excel, the outcomes of the SQL Assertion within the Invoice of Supplies desk change accordingly. In Energy Question, we are able to reference the primary worth of a column in a desk as beneath:

TABLE_NAME[COLUMN_NAME]{0}

So, we use the next expression to get the worth of the StartProductID column from the Parameters desk:

Parameters[StartProductID]{0}

22. Choose the Invoice of Supplies question from the Queries pane
23. Click on the Superior Editor
24. Exchange the unique expression with the next

let
    Supply = Sql.Database(".sql2019", "adventureworks2019", [Query="EXEC [dbo].[uspGetBillOfMaterials] @StartProductID = " & Textual content.From(Parameters[StartProductID]{0}) & ", @CheckDate = '" & Textual content.From(Parameters[CheckDate]{0}) & "'"])
in
    Supply

25. Click on Completed

Relying in your Energy Question privateness settings in Excel, it’s possible you’ll get the next warning:

We get this warning as a result of we’re referencing the Parameters question from the Invoice of Supplies question, whereas these queries are coming from totally different knowledge sources, which suggests we’re doubtlessly sending knowledge from one knowledge supply to a different. This could be a potential privateness breach, therefore Energy Question’s inner firewall blocks the referencing question. In our state of affairs, we are able to ignore the Privateness Ranges. I counsel studying this doc to know the Privateness Stage settings in Energy Question and this one about Privateness Stage Firewall earlier than deciding to disregard the Privateness Ranges.

To disregard the Privateness Ranges, observe these steps:

26. Click on the File menu
27. Click on Choices and settings
28. Click on Question Choices
29. Click on the Privateness tab beneath the CURRENT WORKBOOK part
30. Click on the Ignore the Privateness Ranges and doubtlessly enhance efficiency
31. Click on OK

Now, the Invoice of Supplies question ought to present the outcomes as the next picture exhibits:

Allow us to take a look on the second strategy.

Strategy 2: Parameterising the SQL connector’s SQL Statements, With out Ignoring Privateness Ranges

On this strategy, we don’t load the parameters desk from Excel into Energy Question. As an alternative, we use the Excel.CurrentWorkbook() operate, which supplies us all Excel tables and named ranges within the present workbook. Allow us to have a fast look and see how the Excel.CurrentWorkbook() works.

Utilizing the Excel.CurrentWorkbook() in Energy Question for Excel

As the next picture exhibits, I added some dummy knowledge, value1 and value2, in two cells in Excel. I can create a Named Vary by choosing a number of cells and typing a reputation within the Title Field:

Now we open the Energy Question Editor and undergo the next steps:

1. Click on the Get Information drop down
2. Click on the Launch Energy Question Editor
3. Within the Energy Question Editor window, create a Clean Question by right-clicking the Queries pane and hovering over the New Question > Different Sources > Clean Question

4. Within the formulation bar, kind = Excel.CurrentWorkbook() and commit the change

Within the above picture, the Params desk is the desk we created earlier after we have been creating the primary strategy, which comprises the values we need to go to the SQL Assertion of the SQL connector. To see the contents of every desk, click on on the cell (not on the Desk) as proven within the following picture:

We’re after the worth of the StartProductID column to go to the @StartProducyID parameter and the values of the CheckDate column to go to the @CheckDate parameter of the dbo.uspGetBillOfMaterials saved process in our SQL Assertion. With the next expressions, we are able to the values:

• StartProductID: Excel.CurrentWorkbook()[Content]{0}[StartProductID]{0}
• CheckDate: Excel.CurrentWorkbook()[Content]{0}[CheckDate]{0}

Now that we all know how the Excel.CurrentWorkbook() operate works, and the right way to get the values for the StartProductID and CheckDate, we go forward modifying the SQL Assertion. To have each approaches in the identical file, I duplicate the Invoice of Supplies question. I additionally change the Privateness Stage setting again to default. Observe these steps to implement the second strategy:

1. Choose the duplicated question, Invoice of Supplies (2)
2. Click on the Superior Editor button
3. Exchange the earlier expressions with the beneath one:

let
    Supply = Sql.Database(".sql2019", "adventureworks2019", [Query="EXEC [dbo].[uspGetBillOfMaterials] @StartProductID = " & Textual content.From(Excel.CurrentWorkbook()[Content]{0}[StartProductID]{0}) & ", @CheckDate = '" & Textual content.From(Excel.CurrentWorkbook()[Content]{0}[CheckDate]{0}) & "'"])
in
    Supply

4. Click on Completed

Listed below are the outcomes:

It’s all executed. We will now click on the Shut & Load button from the ribbon.

I just like the second strategy over the primary one, so I unload the Invoice of Supplies question from the PowerPivot mannequin and maintain the Invoice of Supplies (2) question. Now that we efficiently applied the answer, allow us to check it to make sure it really works as anticipated.

Testing the Resolution

Testing the answer is simple. We solely want to alter the values of the parameters on the Excel sheet and refresh the PowerPivot mannequin. We have now two choices to take action.

Choice 1, Utilizing the Queries and Connections pane in Excel

1. Click on the Queries and Connections from the Information tab on the ribbon. At present, the Invoice of Supplies (2) question has 24 rows

2. Change the StartProductID‘s worth from 727 to 802
3. Click on the Refresh button on the Invoice of Supplies (2)

Because the previous picture exhibits, the question now comprises 8 rows. To view the information, hover over the question:

The info within the above picture is loaded into the PowerPivot mannequin, so we are able to at all times take a look at PowerPivot to see the precise knowledge, which takes us to the second strategy.

Choice 2, Utilizing the PowerPivot in Excel

On this strategy, we modify the values within the Excel sheet and refresh the information immediately from the PowerPivot.

1. Click on the Handle Information Mannequin button from the Information tab on the ribbon to open PowerPivot

2. In Excel, change the worth of the StartProductID again to 727
3. Change again to PowerPivot and click on the Refresh button

Lastly, you would possibly ask about how one can reconcile the information in our checks. Properly, we solely must open SQL Server Administration Studio (SSMS) and run the next SQL assertion:

EXEC [dbo].[uspGetBillOfMaterials] @StartProductID = 802, @CheckDate = N'2013-01-01'

That’s it. We made it. I hope you discover this weblog submit useful. When you have questions or feedback, use the feedback part beneath to speak with me.