Table Names.Field Names

[#1]

Hi,

We have literally just upgraded to version 11 from version 10 and we have encountered an issue that hopefully you can offer assistance with.

We have a dashboard built that now doesnt work.  The field names that are available for selection are preceded by the table name. Previously this wasnt the case - so the already built dimensions/expressions are no longer working.

For example a common used dimension previously is Month, however the available field is now Calendar.Month - so the used dimension has a big red cross next to it and not showing on the dashboard.

We have changed our data load from an ODBC to an OLE DB connectio - so dont know if this makes a difference?

Any help greatfully received rather than having to go through all the dimensions/expressions and changing them to the new ones that are coming through.

James

[martinpohl]

is there a "qualify *" in the script or a qualify setting in the odbc connection settings set?

[#3]

Hi,

There is a qualify * after the connection. Is this causing the issue? Please excuse my lack of knowledge and thank you for your assistance.

James

[martinpohl]

yes, that's the reason,

delete this.

[SunilChauhan]

qualify *;

is used for naming like tablename.fieldname

if you want for single table not for other table do likbelow

qualify *;

Table1:

load

fields

from path

unqualify *;

then other load staements

hope this make sense

[#6]

Many thanks to you all for the help. Problem Solved

[SunilChauhan]

what was the problem.

please mark it as helpful or correct

or you post solution for future refrence

[#8]

The problem was the qualify statements that were in the script. Further investigation was that there were multiple qualfiy and unqualfy statements.

These have been deleted in some instances where not required and unqualfiy statements put in elsewhere.