To Unsubscribe from this Discussion, send an e-mail to unsubscribe.development@elinkkc.opentext.com.
Ok, you didn't set a SQL statement in your attribute definition but used the build in feature of attribute lookup, sorry. Perhaps you may try to setup a specific SQL statement in the attribute definition, this would allow you to have better control on the lookup...
Pierre
Hi,
I've encountered similar issue where I had a series of cascading attributes (i.e. select 1st, 2nd, then auto-populate third).
We found that if a source of your data is an integer and only one row is returned, the SQL fails.
Try explicitly setting the SQL on the attribute as follows
Select convert(varchar, X) from Y where.....
Replace X and Y as appropriate.
It seems that if the field isn't explicitly selected by the user (which requires more than one row be present for the values of the attribute), then the SQL fails to convert integer/date (non text) database columns.
Explicitly converting to varchar seemed to fix our issue.
Regards,
David Henshaw
Fastman Consulting & Solutions