SPD2010 not Updating List Items

I am attempting to use a SPD2010 workflow to update a secondary list that is used to present an ongoing history for scorecards. Once a scorecard has been completed the workflow will run and update a score and comments for 25 list item rows based on a title field comparison. The values (stored in a form library) to be copied are a number field and a comment field. The form has the necessary elements for creating the unique Title in the list to be updated as well as the data that is to be passed on.

Form Library field - Type - example:

fAdminLock - Yes\No - Yes

Site - Text - ANST

Department - Text - Assembly

Element Number - text - 1.1

Score - number - 7

Comment - text - 08/14 - Late shipment, 09/03 - double charge

The values (stored in a list) to be copied to are a number field and a comment field. The Title in the list item to be updated is static and is compared using the values from the form.

 List Item field - Type - example:

Title - Text - ANST-Assembly-1.1

20171 - Number - (blank)

Comments - text - (blank)

My SPD 2010 Workflow generates variables for the data by creating the Title string using the form library data. Then the score and the comments variables are filled in. The Update List command is then run using the 3 items. varPoints to 2017 and varComments to Comments in the list.

As a verification of the entries (this actually attempts to update 25 different scores) a log entry is generated which shows all the variables being set and continuing on through the process without any errors. The problem is that only a 0 shows up in the very first List Item entry and then nothing after that.

Resulting log entries:

9/20/2016 8:17 AM	Comment	System Account	Score Write off starting for ANST-Assembly-171...first determine that form is at administrative state...
	9/20/2016 8:17 AM	Comment	System Account	ScoreWriteOff starting for ANST-Assembly-171...The variables defined will now be populated from data based on the score card and the score table.
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-1.1 updated with: 2 and 2016-08-29 - calanas - Monk - The trim process was missed on about 4K units. Attitash 4 - Lead frame damage issue.  Cash CS42L51-CNZR/B0 - stitch broken issue.
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-1.2 updated with: 5 and 2016-08-29 - calanas - Average 8D score of >80% and Cycle time of 14days or less.
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-1.3 updated with: 5 and 2016-08-29 - calanas - No qualification or reliability failures this period.
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-1.4 updated with: 7 and 2016-08-29 - calanas - 2015 Audit Score 78% (5 points), 100% closed in a quarter (+2 points)
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-1.5 updated with: 0 and
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-2.1 updated with: 5 and 2016-08-29 - eguinto - OTD = 98.7% - Total of 811 (out of 822) lots met SOD.
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-2.2 updated with: 4 and 2016-08-29 - eguinto - Average total CT 13 days.  Target < 12 Days.
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-2.3 updated with: 5 and 2016-08-29 - eguinto - Meeting requirements.  Supported additional Dorante CS6422 LTB builds.
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-2.4 updated with3 and 2016-08-29 - eguinto - Average Manufacturing CT = 7.8 Days. Target < 6 Days
	9/20/2016 8:17 AM	Comment	System Account	list item ANST-Assembly-2.5 updated with: 0 and
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-3.1 updated with: 4 and 2016-08-17 - vicg - *
	9/20/2016 8:17 AM	Comment	System Account	list item ANST-Assembly-3.2 updated with: 6 and 2016-08-17 - vicg - No reductions offered this quarter.
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-3.3 updated with: 0 and
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-3.4 updated with: 0 and
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-3.5 updated with: 0 and
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-4.1 updated with: 3 and 2016-08-29 - eguinto - All items > 1.33, however, there are several items < 1.67.
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-4.2 updated with: 3 and 2016-08-29 - eguinto - N / A
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-4.3 updated with: 8 and 2016-08-29 - eguinto - Cumulative assembly yield = 99.86%.(16.050KK/16.073KK)
	9/20/2016 8:17 AM	Comment	System Account	list item ANST-Assembly-4.4 updated with: 0 and
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-4.5 updated with: 0 and
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-5.1 updated with: 8 and 2016-08-29 - eguinto - Supportive and responsive customer service.
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-5.2 updated with: 4 and 2016-08-29 - eguinto - Good support on Lead frame quals and Supplier Development Goals
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-5.3 updated with: 5 and 2016-08-29 - eguinto - Reports are sent on a timely manner and generally accurate.
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-5.4 updated with: 0 and
	9/20/2016 8:17 AM	Comment	System Account	List item ANST-Assembly-5.5 updated with: 0 and
	9/20/2016 8:17 AM	Comment	System Account	Workflow completed...terminating normally.

The record results from List Item 1:

<input id="GroupByColFlag" type="hidden" /><input id="GroupByWebPartID186" type="hidden" webpartid="{0BD8BA13-E5FB-4ABB-9A0E-BA354DA20631}" />

		Title	20171	Comments
		ANST-Assembly-1.1	0

As you can see - the process does not update the list instead placing a 0 in the column with no other changes and yet the workflow continues through withoput being interrupted by errors. I was able to get it to crash and not complete the workflow by forcing field type mismatches (text instead of number and numbers instead of text. This shows me that if it is a field type mismatch that the workflow is not being notified nor is their any SP log data pointing out an error. Any ideas would be appreciated excluding doing things like trying visual studio. SPD 2010 is my only tool so anything else is moot.

Thanks in advance!

Greg

---

Greg McAllister