TM1 Forum

Hi,

I'll preface this with an 'i'm new, be gentle' - i've read the posting tips so hopefully i'll summarise my issue succinctly.

I'm attempting to write a create cube process that reads from an iSeries/JDE table via ODBC link (64bit)

See the screenshot for my issue, but i'm getting pink shaded cells in the preview, and doesn't bring the data into the variables definition tab with the message "WARNING; There are some columns in the query that has been ignored at the variables definition; They are not supported by TM1."

it seems to be for columns that contain strings in the original data source, any ideas what's causing this?

I've checked the TI user guide, the TM1 cookbook and the Official guide to no avail.

Any help is greatly appreciated,

Thanks

Have you tried checking the "Use Unicode" box?

Yes, the preview/error message remains the same with the unicode box ticked/unticked.

Then it sounds like you've got a data type or characters in the field(s) that are not supported by TM1. Have you tried outputting the query to a text file to see what's actually in those fields? How long is the text in those fields? Does it possibly contain some strange characters? Just things to consider. Good luck.

I do indeed know what data is in the columns. If I output the table to a csv file and use that, it is all readable with no issues.

For example...

the column GBLT above contains either "AA" or "BA" - nothing more.

Any ideas?

What DataType are these columns defined as?

Have you tried to convert them to something else in the query? Maybe do a concatenation for testing? Or possibly do a hard coded value in the select just to test that there is not something strange going on with the odbc driver.

Thanks for your assistance guys, it appears we've solved the issue.

It was a ODBC driver configuration setting that needed to be activated - specifically in ODBC Driver Configure -> Conversions tab, there is an option titled “Convert Binary data (CCSID 65535) to text” - This gave me readable string data in these fields.

Thanks again for your input,

Simon