Ninja Property

Hi,

I've read about Ninja Properties and started using them. Works great! Now I have a problem which I'll try to describe.

Part of my model:

Part of the Vsrcategory partial class:

    public partial class Vsrcategory
{
    public string TranslatedName
    {
        get { return TranslatedNameExpression.Compile()(this); }
        set
        {
            this.SetLookupValue("Name", value);
        }
    }

    private static readonly Expression<Func<Vsrcategory, string>> TranslatedNameExpression = v => v.Name.Name;

I can now filter and sort on the TranslatedName property in my queries. The big idea however is that I want to translate the name property into various languages. This is where LookupTranslation comes in.

I'd like to do somethimg like this:

    public partial class Vsrcategory
{
    public string TranslatedName
    {
        get { return TranslatedNameExpression.Compile()(this, Thread.CurrentThread.CurrentUICulture.Name); }
        set
        {
            this.SetLookupValue("Name", value);
        }
    }

    private static readonly Expression<Func<Vsrcategory, string, string>> TranslatedNameExpression = (v, c) => // LOST!

Is this at all possible? If so, could you give me a hint on how to implement this expression? fyi: I'm using LightSpeed 5, nightly build 20131123

Regards, Diego

If I understand you correctly you are looking to fetch the LookupTranslation which matches the Lookup entry for the given culture? If thats correct you wont be able to handle this with a ninja property as this only allows you to work with local expressions and not a sub-query or a property from a joined entity.

You could implement the property with an independent fetch call which performs the query against Lookup joining against LookupTranslation however that is going to result in a query per property which is generally going to perform very badly if every use this in a set based operation. Have you looked at handling this at the server and surfacing these entities through a view or a stored proc instead?

Jeremy