on 12-25-2017 6:50 AM
Hi Sunil,
Association can't be used where it's defined, it's not the association purpose.
you have two options:
1, you have a higher level CDS for the current one, then you could use the association freely.
or 2, you switch the association to leftouter join.
Best Regards,
Sean
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Sunil,
Looks like the issue is because of the usage of $projection.For details, please see Horst Keller's comment from April 19,2017 in response to the comment by Ceyhun Alp here
Best,
Aashrith.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you find a solution to this ? The Association can be exposed but the direct fields can't be used ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There will be a problem that on using the _vbep.wmeng as Orderqty defining in the higher level view that if the higher level view is a Query view because the definition is not recognised by the ODP and will throw the error "Cannot Resolve name in the ODP" , so in such case create one more new higher level view view2 to the current view view1 and use the association to vbep in that view2 and define the field from vbep. use that view2 as the source view to query view instead of the view1..
Thanks
LNV
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.