
In September 2014, I wrote a weblog put up 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 in the event you’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 believed 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 put up.
The Downside
Every so often, Excel customers require to get the info 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?
Conditions
For this weblog put up, I take advantage of SQL Server 2019 and Microsoft’s well-known pattern database, AdventureWorks2019. You’ll 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 Answer
I talk about 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 method requires ignoring the Privateness Ranges in Energy Question, whereas the opposite doesn’t. Each approaches work, however, relying in your preferences, you could want one over the opposite.
As talked about, I take advantage of the AdventureWorks2019 pattern database that comprises a few saved procedures. I take advantage of the dbo.uspGetBillOfMaterials saved process accepting two parameters, @StartProductID and @CheckDate.
Strategy 1: Parameterising the SQL connector’s SQL Statements, Ignoring Privateness Ranges
Comply with these steps to go the parameters’ values from an Excel sheet to the saved process and get the ends in Excel:
- In Excel, navigate to the Knowledge tab
- Click on the Get Knowledge dropdown
- Hover over the From Database choice and click on the From SQL Server Database
- Enter the Server
- Enter the Database
- Increase the Superior choices
- Kind
EXEC [dbo].[uspGetBillOfMaterials] @StartProductID = 727, @CheckDate = N'2013-01-01'within the SQL assertion textbox - Click on OK
- Click on the dropdown on the Load button
- Click on Load to

From right here, we now have some choices to load the outcomes both into an Excel sheet or the PowerPivot knowledge mannequin. We wish to load the info into the PowerPivot knowledge mannequin on this instance.
- Choose Solely Create Connection
- Test the Add this knowledge to the Knowledge Mannequin choice
- Click on OK
- Rename the question to Invoice of Supplies
- On the Rename Question warning, click on the Rename button
- The concept is to go the parameters’ values from an Excel sheet, so I sort the next into the Sheet1:
- Choose the vary we entered within the earlier step
- Click on the From Desk/Vary from the Knowledge tab
- On the Create Desk window, be sure that the My desk has headers is ticked
- Click on OK. This navigated us to the Energy Question Editor window
- Rename the brand new question to Parameters
We now wish to change the SQL Assertion of the Invoice of Supplies question to get the values from the related columns within the Parameters desk. Subsequently, every time the person adjustments the values on Excel, the outcomes of the SQL Assertion within the Invoice of Supplies desk change accordingly. In Energy Question, we will 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}
- Choose the Invoice of Supplies question from the Queries pane
- Click on the Superior Editor
- Substitute 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
- Click on Completed
Relying in your Energy Question privateness settings in Excel, you could 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 completely different knowledge sources, which implies we’re probably sending knowledge from one knowledge supply to a different. This is usually a potential privateness breach, therefore Energy Question’s inside firewall blocks the referencing question. In our situation, we will ignore the Privateness Ranges. I recommend 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:
- Click on the File menu
- Click on Choices and settings
- Click on Question Choices
- Click on the Privateness tab beneath the CURRENT WORKBOOK part
- Click on the Ignore the Privateness Ranges and probably enhance efficiency
- Click on OK

Now, the Invoice of Supplies question ought to present the outcomes as the next picture reveals:
Allow us to take a look on the second method.
Strategy 2: Parameterising the SQL connector’s SQL Statements, With out Ignoring Privateness Ranges
On this method, we don’t load the parameters desk from Excel into Energy Question. As an alternative, we use the Excel.CurrentWorkbook() operate, which provides 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 reveals, 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:
- Click on the Get Knowledge drop down
- Click on the Launch Energy Question Editor
- 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
- Within the system bar, sort
= Excel.CurrentWorkbook()and commit the change
Within the above picture, the Params desk is the desk we created earlier after we had been creating the primary method, which comprises the values we wish 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 will 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. Comply with these steps to implement the second method:
- Choose the duplicated question, Invoice of Supplies (2)
- Click on the Superior Editor button
- Substitute 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
- Click on Completed
Listed here are the outcomes:
It’s all finished. We are able to now click on the Shut & Load button from the ribbon.
I just like the second method over the primary one, so I unload the Invoice of Supplies question from the PowerPivot mannequin and preserve 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 Answer
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’ve got two choices to take action.
Possibility 1, Utilizing the Queries and Connections pane in Excel
- Click on the Queries and Connections from the Knowledge tab on the ribbon. Presently, the Invoice of Supplies (2) question has 24 rows
- Change the StartProductID‘s worth from 727 to 802
- Click on the Refresh button on the Invoice of Supplies (2)
Because the previous picture reveals, the question now comprises 8 rows. To view the info, hover over the question:
The information within the above picture is loaded into the PowerPivot mannequin, so we will all the time take a look at PowerPivot to see the precise knowledge, which takes us to the second method.
Possibility 2, Utilizing the PowerPivot in Excel
On this method, we alter the values within the Excel sheet and refresh the info instantly from the PowerPivot.
- Click on the Handle Knowledge Mannequin button from the Knowledge tab on the ribbon to open PowerPivot
- In Excel, change the worth of the StartProductID again to 727
- Change again to PowerPivot and click on the Refresh button
Lastly, you may ask about how one can reconcile the info in our exams. Effectively, 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 put up useful. In case you have questions or feedback, use the feedback part beneath to speak with me.
Associated
Uncover extra from BI Perception
Subscribe to get the newest posts despatched to your electronic mail.



















