Alias column in presentation layer throwing nonexistent column error

1391185

Hi

We have few columns which renamed later, defined alias in presentation layer.

Report created with old names are now throwing error nonexistent column even though old name mentioned in alias.

Please help.

Thanks

SonPat99

Hi,

Can you please share the details, like the environment details, error screens, etc.?

1391185

Hi

The column "Industry SIC" is rename to "Primary Industry Code" in presentation layer and old name mentioned in Alias.

Reports are already developed using alias name. while generating those reports getting below error eventhough name is mentioned in alias.

Robert Angel

Hi,

you don't have to change anything in the reports when you alias a column in the presentation layer, it just works without a rewrite.

So you either need to go back to the prechanged version of the report(s) or refresh the field(s) in question in the report.

SonPat99

Can you also share a screen of the Presentation layer (the alias) as well?

As Robert highlighted, you do not have to do anything post creating a alias in Presentation Layer.

1391185

Hi SonPat,

"Primary Industry Code" is having alias name as "Industry SIC" as per below screenshot. Still getting error mentioned above for same column.

Thanks

Thomas Dodds

Does the alias have a trailing space?  Just looking at obvious points where the lookup will fail ...

[Deleted User]

It's looking up Industry."Industry SIC". Your Presentation Column has a FQN (fully qualified name) of "Primary Industry"."Industry Code" if you take into account the table name. Is the table aliased as well?

SonPat99

Hello,

Your Table name from the initial screen shot is "Industry"

But, from the new screenshot, you are referring to table "Primary Industry"

As highlighted by Christian Berg, I think this is causing the problem. Have you renamed the table as well...?

1391185

Hi All,

Yes the table name was not aliased. Its working fine now after giving alias name to the presentation table.

Thanks for all your help and Support.

[Deleted User]

Good to hear. Watch out for aliases - they are a huge pain in the long run and make maintenance and lifecycle-management a real chore since no one knows which combination of "name"."alias"."name" or "alias"."alias"."alias" or "alias"."alias"."name". etc etc etc gets used and where.