You are viewing limited content. For full access, please sign in.

Question

Question

Two Custom Queries - Insert statement

asked on September 8, 2016 Show version history

I have developed a workflow that inserts two sets of time values for hours worked into an SQL database.  This means we have two start times and two end times.  An example would be as follows.

07:00 - 12:00  13:00 - 16:00

I have created a Custom Query for each begin and end time submission to submit the times to the database. 

Each time has a metadata field in LaserFiche of startShift, endShift, startShift2, endShift2. 

The workflow performs custom query 1, then moves on to custom query 2 if a value has been provided for startShift2 or endShift2.

When custom query 2 is ran, it is inserting the same data from customer query 1. 

I have made sure that the queries are pulling data from the correct RetrieveFieldValues and have even changed the name of the parameters in the queries.   

I have placed the queries into separate workflows with "End Workflow" options ; however, I still only get the values from startShift, and endShift for both queries. 

On Custom Query 2, I have even removed the RetrieveValueFields for startShift and endShift.  

I am completely lost how custom query 2 is still pulling the values for startShift and endShift. 

Does anyone have any suggestions?

 


 

 

0 0

Replies

replied on September 8, 2016

What you are doing looks right and makes sense. My recommendation would be to add a bunch of Track Token processes to each of your workflows at the end and figure out where exactly it is going wrong. This will log all values each time a track activity is called so you can look at all values once the workflow is completed.

My only explanation is that your workflow is actually being invoked twice, recording the first value twice, and the second query is not even running at all.

 

0 0
replied on September 14, 2016

What does the condition evaluation look like for the "Determine if the second shift is needed" branch?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.