Hello CAPM Experts,
in my post Issues with semantic navigation using OData V2 Services based on CAP(M) I've described an issue that I've faced and solved when using project local persistency. But the application that I'm developing uses an existing persistence which I've annotated with:
But using this combined with the virtual attribute:
virtual semanticURLtoFinancialContract : String;
Results in the error message:
invalid column name: SEMANTICURLTOFINANCIALCONTRACT
Is such a use intended and is the current behaviour a bug?