Query Data Activity in Workflow

asked on April 30, 2013 • Show version history

I am having a problem getting the Query Data activity to work for me.

I have an Excel Spreadsheet (also attached)

For the data source I used a direct connect to the spreadsheet. In the Query Criteria I choose the Run column with a value of “run” – when I test the query it comes back with 0 rows affected. Shouldn’t it have come back with at least 11? For Rows To Return I choose all rows.

I had this working but it would only find some of the records – for example it would find the 1 Acker Drive but not 13 Woodland Drive. So I started with a clean slate. The goal is to “read” the New SBL field from a LF template field and look it up then populate the OldSBL and StreetNumber and Address on my template.

Attached is a briefcase so you have the template, the exported workflow and the Excel spreadsheet. From everything I’ve read I have everything set up correctly but it will not work so I must be missing something. Thanks for your help!

image002.jpg (9.58 KB)

| Download

image003.png (8.9 KB)

| Download

0 0

APPROVED ANSWER

replied on May 2, 2013 • Show version history

I had some time to test your lookup and I was able to reproduce your results, and I have a solution for you. From what I can tell, two things are at play here. The first is that there is currently an issue with the ‘test’ process in workflow for lookups to excel sheets causing it to display ‘0’ regardless of the lookup working or not. This doesn’t affect functionality at all, because the workflow will still run correctly even if the test returns 0 rows. The second issue here is that there is something not quite right with your .xls file. In general Workflow and Excel aren’t the best of friends due to the limitations of Excel, so we recommend against using it for a production environment (Excel only allows one concurrent connection and Workflow is multi-threaded). I was able to save your data as a .csv file instead of .xls and reconfigure the lookup and it worked perfectly. Try saving the file as a .csv and it should work, if you run into issues with the workflow once the lookup is working I would recommend perhaps getting the data into a Sql table.

0 0

Question

Question

Answer

Replies

Sign in to reply to this post.