cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
kokitabayashi
Advocate I
Advocate I

Results from SQL query using subquery is blank

I'm currently running SQL command using Excel ODBC Driver and trying to run layers of JOIN statements using subquery but facing an issue.

 

I ran the same SQL query on My SQL DB via MySQL Workbench and that one worked as expected but, the same query with the same data running on PAD with Excel ODBC Driver gives me different (and unexpected) results.

 

What I'm trying to do overall: Join two tables trying multiple columns one by one using subqueries.

 

High level steps (my question is a subset of the step 1 and 2):

1. Join TBL_1 and TBL_2 with column 'A' => Keep the matched result (will call Res_X here) and unmatched result (will call Res_D here)

2. Join TBL_1 and Res_D (unmatched result from step 1) with column 'B' => Keep the matched result (will call Res_Z here) and unmatched result

3. Union ALL Res_X (matched result from step 1) and Res_Z (matched result from step 2)

4. Do the same operation using column 'C' and Union All the matched results (continue total four times)

 

Following is the test tables I'm using:

[TBL_1]

COL_ACOL_B
1001
1012
1023
1035
1046
1057
1068

 

[TBL_2]

COL_CCOL_D
100A
101B
102C
5D
601E
701F
10ABXXX801YYY
11ABCXXX801YYY

 

[Expected result (run query with unmatched result which is a subset of what I'm trying)]

c.COL_Ac.COL_BCOL_CCOL_Dd.COL_Ad.COL_A
  5D1035
  601E  
  701F  
  10ABXXX801YYY  
  11ABCXXX801YYY  

 

[Connection String]

kokitabayashi_0-1660276656733.png

As some columns have mixed data, I put "IMEX=1" in the connection string.

 

[SQL Query]

kokitabayashi_1-1660276722622.png

As some columns have mixed data, ON c.[COL_C] = d.[COL_B] returned an error. Because of it, I used LIKE without any wildcard to join two tables.

 

[Result from the SQL Query]

kokitabayashi_2-1660276851098.png

As you can see, the first JOIN statement is working and returning 5 rows but the second JOIN statement which is connecting the results from the 1st JOIN and the original table 1 is returning blank.

When I run this on MySQL via MySQL Workbench, it returns value for d.COL_A and d.COL_B as expected (103 and 5).

 

 

Following are some experiments I also did to specify where the issue is coming from.

 

If I run the subquery separately, the result looks like this (looks fine).

[Sub query only]

kokitabayashi_3-1660277414494.png

[Result when running sub query only]

kokitabayashi_4-1660277454576.png

 

If I just join the two tables using the soma column without using subquery, the result looks like this (looks fine).

[Query which is just joining two tables]

kokitabayashi_12-1660279262288.png

 

[Result from running the query which just join two tables]

kokitabayashi_6-1660277705503.png

 

If I flip the order of the original query it gave me different result (which is also confusing)

[Flip the order]

kokitabayashi_10-1660279037328.png

 

[Result from flipped SQL]

kokitabayashi_11-1660279094026.png

 

 

Based on the original result, result from MySQL and additional experiments, I'm assuming the issue is coming from how the subquery works on PAD & Excel ODBC combination.

 

Would be great if anyone could provide me an insight on this!

Thanks!

 

2 ACCEPTED SOLUTIONS

Accepted Solutions
ZS440
Resolver III
Resolver III

Hi.

@kokitabayashi 

Sorry I can't help you, but I have verified this.

In my environment, your Query works fine.

If there is any difference from my environment, you may have a clue.

 

Windows 10 Pro 21H2

Microsoft Excel for Microsoft 365 MSO (Version2207 Build 16.0.15427.20182) 64 bit 

Power Automate for desktop Version 2.22.263.222.02 Installer Edition

CleanShot 2022-08-13 at 12.09.16@2x.pngCleanShot 2022-08-13 at 12.10.46@2x.png

 

 

CleanShot 2022-08-13 at 12.13.32@2x.png

CleanShot 2022-08-13 at 12.15.15@2x.png

Underscores in column names are omitted, but it works fine.

CleanShot 2022-08-13 at 12.58.37@2x.png

In my opinion, it is better not to use underscores(_) in column names.

Because when using the Microsoft Office Access Database Engine OLE DB Provider, underscores act as ANSI SQL wildcards.

 

https://docs.microsoft.com/en-us/office/client-developer/access/desktop-database-reference/compariso...

 

I can use "=" instead of "LIKE" if I do not use IMEX=1 for Extend Properties and the Excel data source is explicitly formatted as text type.

 

I hope it works out for you.

View solution in original post

ZS440
Resolver III
Resolver III

Hi @kokitabayashi 

Thank you for sharing your various verifications and results with us.
Thank you too.

 

However, I believe we need to be careful about IMEX=1.
IMEX=1 is telling the driver to read the data as text, but we are having problems.
I think we can confirm this by trying the following mixed data.

CleanShot 2022-08-14 at 13.45.04@2x.png

CleanShot 2022-08-14 at 13.52.43@2x.png


If there are more than 8 numerical values in a row and then text values are mixed, reading will fail and result in null, even though IMEX=1.

 

CleanShot 2022-08-14 at 13.51.38@2x.png
Therefore, I think it would be safe to pre-cleanse the data source side (EXCEL in this case) to text type data.

CleanShot 2022-08-14 at 13.58.00@2x.png

No use the IMEX=1 option.

CleanShot 2022-08-14 at 13.59.25@2x.png

Similarly, by data formatting all columns to text type, your query can be executed using "=" without the IMEX option.

CleanShot 2022-08-14 at 14.16.13@2x.pngCleanShot 2022-08-14 at 14.16.20@2x.png

CleanShot 2022-08-14 at 14.20.31@2x.png

CleanShot 2022-08-14 at 14.21.32@2x.png

If you do not want EXCEL to format your data, you can also explicitly enable IMEX=1 by setting HDR=NO. This will cause the first row of data to be the original column name and the entire column to be text type as well. (If the column name is a text type)

 

CleanShot 2022-08-14 at 14.47.57@2x.png

I hope this helps you or anyone else.

 

 

View solution in original post

5 REPLIES 5
ZS440
Resolver III
Resolver III

Hi.

@kokitabayashi 

Sorry I can't help you, but I have verified this.

In my environment, your Query works fine.

If there is any difference from my environment, you may have a clue.

 

Windows 10 Pro 21H2

Microsoft Excel for Microsoft 365 MSO (Version2207 Build 16.0.15427.20182) 64 bit 

Power Automate for desktop Version 2.22.263.222.02 Installer Edition

CleanShot 2022-08-13 at 12.09.16@2x.pngCleanShot 2022-08-13 at 12.10.46@2x.png

 

 

CleanShot 2022-08-13 at 12.13.32@2x.png

CleanShot 2022-08-13 at 12.15.15@2x.png

Underscores in column names are omitted, but it works fine.

CleanShot 2022-08-13 at 12.58.37@2x.png

In my opinion, it is better not to use underscores(_) in column names.

Because when using the Microsoft Office Access Database Engine OLE DB Provider, underscores act as ANSI SQL wildcards.

 

https://docs.microsoft.com/en-us/office/client-developer/access/desktop-database-reference/compariso...

 

I can use "=" instead of "LIKE" if I do not use IMEX=1 for Extend Properties and the Excel data source is explicitly formatted as text type.

 

I hope it works out for you.

kokitabayashi
Advocate I
Advocate I

Thank you so much for your reply, @ZS440 

This is indeed, really helpful!

 

The following was the environment I was using when I originally posted.

 

** Original Test (Test-A) **

[Test Environment-A]

Windows 10 Enterprise 20H2

Microsoft Excel for Microsoft 365 MSO (Version 2108 Build 16.0.14326.21052) 64-bit

PAD Version 2.16.215.22020

 

[SQL & Connector]

(Refer to the original post)

 

[Result in the Test Environment-A (as posted in the original post)]

kokitabayashi_0-1660436436694.png

 

Based on your reply, I did the following additional experiments and got interesting results.

 

** Additional Test (Test-B) **

[Test Environment-B]

Windows 10 Pro 21H2

Microsoft Excel for Microsoft 365 MSO (Version 2207 Build 16.0.15427.20182) 64-bit

PAD Version 2.22.263.22202

 

[SQL & Connector]

(Same with the original one: Refer to the original post)

 

[Result in the Test Environment-B]

kokitabayashi_1-1660436825432.png

 

** Additional Test (Test-C) **

[Test Environment-C]

Windows 10 Pro 21H2
Microsoft Excel for Microsoft 365 MSO (Version 2207 Build 16.0.15427.20182) 64-bit
PAD Version 2.21.244.22174

 

[SQL & Connector]

(Same with the original one: Refer to the original post)

 

[Result in the Test Environment-C]

kokitabayashi_2-1660437016254.png

 

As you can see, in the two additional environments (Test-B and C), I got the same results as yours (which was what I was originally expecting).

For these additional tests, I created a new bot and new excel file from scratch in the original environment (Test-A) as well, just in case, but the result was the same ("d.COL_A" and "d.COL_B" are blank).

 

It seems like not only PAD version is different but also Windows 10 Pro version and Excel versions are also different; therefore, I cannot conclude which exactly software version difference is causing the issue, but at this moment, considering the maturity of the software and the number of users of it, I'm guessing it may be a bug in PAD version 2.16.215.22020.

 

 

Also, thank you for sharing your opinion on using the underscore in column names and also sharing the results of trying = without IMEX=1 instead of LIKE with IMEX=1.

 

I didn't know about what you mentioned about the underscore with ODBC and it sounds like I should stop using it whenever I have an option. It is great to know that.

 

 

For the use of = instead of LIKE without IMEX=1, I tried as the following but, it seemed like some data were dropped.

 

** Experiment of = without IMEX=1 **

[Connector]

kokitabayashi_3-1660438601575.png

[SQL replaced LIKE with =]

kokitabayashi_4-1660438644443.png

 

[Result (from Environment-A)]

kokitabayashi_5-1660438674722.png

 

[Result (from Environment-B)]

kokitabayashi_6-1660438819519.png

 

As you can see, in the both environments, some data from COL_C were dropped. As I still need these data in the later steps, I tried to figure out the solution and came up with using LIKE with IMEX=1, but if you see any risk doing this way (or any other better way to do it), it would be great if I could hear it!

 

Thank you!

 

ZS440
Resolver III
Resolver III

Hi @kokitabayashi 

Thank you for sharing your various verifications and results with us.
Thank you too.

 

However, I believe we need to be careful about IMEX=1.
IMEX=1 is telling the driver to read the data as text, but we are having problems.
I think we can confirm this by trying the following mixed data.

CleanShot 2022-08-14 at 13.45.04@2x.png

CleanShot 2022-08-14 at 13.52.43@2x.png


If there are more than 8 numerical values in a row and then text values are mixed, reading will fail and result in null, even though IMEX=1.

 

CleanShot 2022-08-14 at 13.51.38@2x.png
Therefore, I think it would be safe to pre-cleanse the data source side (EXCEL in this case) to text type data.

CleanShot 2022-08-14 at 13.58.00@2x.png

No use the IMEX=1 option.

CleanShot 2022-08-14 at 13.59.25@2x.png

Similarly, by data formatting all columns to text type, your query can be executed using "=" without the IMEX option.

CleanShot 2022-08-14 at 14.16.13@2x.pngCleanShot 2022-08-14 at 14.16.20@2x.png

CleanShot 2022-08-14 at 14.20.31@2x.png

CleanShot 2022-08-14 at 14.21.32@2x.png

If you do not want EXCEL to format your data, you can also explicitly enable IMEX=1 by setting HDR=NO. This will cause the first row of data to be the original column name and the entire column to be text type as well. (If the column name is a text type)

 

CleanShot 2022-08-14 at 14.47.57@2x.png

I hope this helps you or anyone else.

 

 

Hi @ZS440 ,

Thank you for sharing your insights and pointing out the potential risk relying on IMEX=1!

 

I tried what you explained about IMEX=1 on my end and was able to recreate the issue ("1hundred8" and "ten" disappear), as well. This is actually, an interesting and also a big problem.

 

Also, the solution you suggested (convert the columns to Text format, stop using IMEX=1, and Join on '=') worked great, as well.

I added a "Run VBScript" action for changing the columns' format to Text before running the SQL statement and everything is working great right now.

 

'Opens the Excel file'
Set objExcel = CreateObject("Excel.Application")
Set objWorkbook = objExcel.Workbooks.Open("%ExcelFile%")
objExcel.Application.Visible = False

'Selects the sheet 1'
Set objSheet = objWorkbook.Sheets("%SheetName%")

'Change the number format of the row to Text'
for col=1 to 2
objSheet.columns(col).NumberFormat = "@"
next

'Selects the sheet 2'
Set objSheet = objWorkbook.Sheets("%SheetName2%")

'Change the number format of the row to Text'
for col=1 to 2
objSheet.columns(col).NumberFormat = "@"
next

'Saves and closes the Excel file'
objWorkbook.Save
objWorkbook.Close SaveChanges = True
objExcel.Application.Quit
Set objExcel = Nothing

 

Thanks!

ZS440
Resolver III
Resolver III

Hi. @kokitabayashi 

I'm glad it worked out for you.

I have learned a lot from you as well.
Thanks for sharing your great idea of using VBScript to change the formatting.

Helpful resources

Announcements

Celebrating the May Super User of the Month: Laurens Martens

  @LaurensM  is an exceptional contributor to the Power Platform Community. Super Users like Laurens inspire others through their example, encouragement, and active participation. We are excited to celebrated Laurens as our Super User of the Month for May 2024.   Consistent Engagement:  He consistently engages with the community by answering forum questions, sharing insights, and providing solutions. Laurens dedication helps other users find answers and overcome challenges.   Community Expertise: As a Super User, Laurens plays a crucial role in maintaining a knowledge sharing environment. Always ensuring a positive experience for everyone.   Leadership: He shares valuable insights on community growth, engagement, and future trends. Their contributions help shape the Power Platform Community.   Congratulations, Laurens Martens, for your outstanding work! Keep inspiring others and making a difference in the community!   Keep up the fantastic work!        

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (4,964)