Subject:"Value can not be converted to requested type" error again Author:guy-francis vella Date:14 Jun 2009 06:26 AM Originally Posted: 14 Jun 2009 06:21 AM
Evening All
I have had this error before "Value can not be converted to requested type" but last time it related to a caching issue between Stylus and SQL and a changed view. I rebuilt the section of the query related to that view and the issue went away
This time I have three xqueries drawing on the same views for the same data. The only difference between the three is a filter at the top level that breaks the data up into "Nab Cardfast", "NAB Direct Debit" and "Checque Receivable". However; if I remove the links to the Asset Combined Data HL view (which is not related to filter and is the same regardless) I don't get this error.
I have tried rebuilding the xquery in case it was a repeat of the caching issue: no joy.
I have eliminated all the fields i am importing from Asset Combined Data HL view one at a time in case it was one particular field that had the issue: no joy. In fact i get the error if no fields are mapped and just the flowr link to the 42 Contract view exists.
I am at a complete loss. Pls find attached the xqueries and a copy of the Asset Combined Data HL view data as seen by Stylus.
Subject:"Value can not be converted to requested type" error again: more files Author:guy-francis vella Date:14 Jun 2009 06:28 AM Originally Posted: 14 Jun 2009 06:27 AM
For some reason not all the files would upload; lets try again.
Subject:No Topic Author:Minollo I. Date:14 Jun 2009 08:45 AM
To help you here we really need the DDL of the views and/or tables you reference from your XQuery:
- Asset_Combined_Schedules_HL_Balanced
- Asset_Combined_Data_HL
- All_HL_Businessv2_Data
- 42_Contract_Data
We had changed one field in the party view from datetime to text. This caused the error for some of the xqueries; the problem occurred where the changed field was not referenced. The problem went away if I deleted the Asset view, which is not related in anyway to the party view. It would also go away if i mapped the changed field in those xqueries where it was not previously mapped.
As I did last time I changed the name of the Party view and then redirected all my xqueries to the new name and the problem disappeared.