Table of Contents

KB Item 305

Product

VERSAGO

Product Version (if applicable)

All

Issue

Actions defined in customPostExecute procedure for a form do not execute as expected.

Symptom

Actions are defined in the customPostExecute stored procedure for a form.  No errors are raised when the record is saved, and the data is posted to the target table(s).  However, the defined actions do not occur.

Cause

The values coming from the form are in an XML string.  These values are case sensitive.  If the case used in the statement to get the value does not match the case of the identifier in the XML, the processing simply does not work.

Resolution Notes

<p>Example<br />The value of the item in the XML string is “vgoRecnum” (lower case “n”) and this is the item we need to obtain to do our processing.</p><p>If the statement to get the value looks like this:<br />&nbsp;SELECT&nbsp; @vgoRecNum = frm.value('(vgoRecNum)[1]','nvarchar(20)') FROM @FormData.nodes('/formData') AS HDR(frm);</p><p>Nothing will be returned since the case of frm.value tiem does not match the XML string since it has uses an upper case “N”.</p><p>If instead we use:<br />SELECT&nbsp; @vgoRecNum = frm.value('(vgoRecnum)[1]','nvarchar(20)') FROM @FormData.nodes('/formData') AS HDR(frm);</p><p>the value we need will be returned because the case of the frm.value item in the SELECT statement matches the case of the item in the XML.</p>

KB Type

Solution

Item Date

13 Dec 2017