Missing Calculated Fields SQL Server [Navision]

[#1]

Hi All,

I'm having troubles with Calculated Fields in all tables, they not appear in the fields list in Select Wizard !!

i'm use SQLOLEDB, Database is SQL Server (Navision) and QV 9 SR2 64 bit.

Is necessary an OLEDB configuration?

Any idea what could be wrong ?

Thanks in advance,

Regards,

JaL

[amars]

Hi JaL

Give an alias to the expression in your SQL statement. Qlikview can not understand which name to give to the Calculated Field. So that is happening.

With Regards

Amar

[#3]

Hi Amar.

thanks for your answer, But... this is not my problem, the calculate Field was made from SQL, not in Script...

Thanks anyway,

JaL

[Miguel_Angel_Baeyens · Accepted solution]

Hello,

Even if they are not shown in the dialog you can anyway load them by writing their names in the load statement that precedes the sql select statement for your sql server database. By the way, are you looking at views, tables, stored procedures?

Regards.

[#5]

that's work.

thank you very much, Miguel

KR,

JaL

[#6]

Hi Miguel,

What do you mean by :

"...writing their names in the load statement that precedes the sql select statement for your sql server database"

I'm also having this issue with Navision, say for example the Customer  has a calculated field of "Balance".

When you look at the SQL Table fields it is not visible, I tried to add the field in the Select statement manually but its says invalid column name.

Thanks ~skip

[Miguel_Angel_Baeyens]

Hi Skip,

So called flow fields are not visible because they are not actually stored into the SQL Server. They are indexes using SIFT and VSIFT Microsoft technologies, and are only available when connecting through native ODBC Navision driver, which in turn is only available for native Navision databases instead of SQL Server databases.

So in short, you will need to create the same logic as in your flowfield but in the QlikView script, or create some trigger to store that value in some other table/field so you can read it using the SQL Server connection you are already using to connect to Navision.

Hope that makes sense.

Miguel