I recently had an issue with a form where the form entries where no longer appearing. It took a while to work out but the issue was caused by one of the field names starting
with a number.
Interestingly if you do start a field with a number the system adds the letter ‘n’ before the number in the ‘xml’
file.
So the column ‘100 Wool felt
stack’ was fine
<n100woolfeltstack></n100woolfeltstack>
However the column ‘£50 voucher
@ the bramble patch’ caused this problem. This is because the £ sign is stripped
for being neither a letter or a number and because the 5 was the second number
an ‘n’ wasn’t added to the start of the xml tag.
Renaming the field and an update of the database solved the problem
UPDATE [database].[UFRecordsXml]
SET [xml] = CAST(REPLACE(CAST([xml] as NVarchar(MAX)),'50voucherthebramblepatch','fiftypoundvoucherthebramblepatch') AS NText)
However please could you fix the bug as obviously it's way over any editors head!!
Contour Bug - Disappearing Entries
I recently had an issue with a form where the form entries where no longer appearing. It took a while to work out but the issue was caused by one of the field names starting with a number.
Interestingly if you do start a field with a number the system adds the letter ‘n’ before the number in the ‘xml’ file.
So the column ‘100 Wool felt stack’ was fine
However the column ‘£50 voucher @ the bramble patch’ caused this problem. This is because the £ sign is stripped for being neither a letter or a number and because the 5 was the second number an ‘n’ wasn’t added to the start of the xml tag.
Renaming the field and an update of the database solved the problem
UPDATE [database].[UFRecordsXml]
SET [xml] = CAST(REPLACE(CAST([xml] as NVarchar(MAX)),'50voucherthebramblepatch','fiftypoundvoucherthebramblepatch') AS NText)
However please could you fix the bug as obviously it's way over any editors head!!
I would like to point out that this is the case in the latest version of Contour, now discontinued.
So if you are maintaining a Contour installation chances that you'll encounter this at some point.
is working on a reply...