Database View, dot.walked field, without including the field

[brian_]

I am building a database view to give a group restricted access to table data. I'm only including fields to which they are allowed to see (sensitive information).

One of the data points they require comes from a dot.walked field, or a join. I can add that separate table to the view and set up the where clause, but the view fails to work unless I include the initial field from which it is dot.walked. The problem is they don't get permission to see that field.

For instance, I have a reference field called Account, that is referring to my Customer_Accounts table.
In Customer_Accounts there is a field called Currency.
I want to include the Account.Currency value without including Account.

Is this possible at all?

Not including the Account field results in this error. Including it causes the view to work properly.

[Brian Lancaster · Accepted solution]

No I don't think there is a way to include a field that is dot walked without including the reference field.  I'm wondering though if you give these users a role that removes there permission to read the particular fields would make more sense rather then trying to create a database view.

[Ankur Bawiskar]

@brian. 

dot walking won't work in database where clause.

Also regarding showing dot walked fields on the database view table please check below link

Using two consecutive dot-walked field of a Database view causes the columns to show empty values fo...

Regards
Ankur

[Ivano Genovese]

I'm experiencing the same issue, but the article is not available anymore, anyone knows how this could be solved?

[Bhavana Reddy]

Did you find the solution for that? if so can you please share it with us