Default value for a lookupTablePath?

dave_cowden

How do you set the default value for a lookup table path? 

When i set up a lookupTable path variable, i expect the default value to be the one selected via the 'default'
clause in the lookup table itself.

But what i find is that the value is empty until the user chooses a value from it, at which point, it is populated.

What is the right way to ensure that the initial value of a lookupPath definition field is set to the default values initially displayed?

ilya_baran

The hole feature regen doesn't look at the lookup table.  Only editing logic does and it only looks for changes to it -- and after the first change, the value passed in is correct.

ilya_baran

I'm not seeing that -- when I type the following, I get a correct default.

const lookupTable = {
        "name" : "choice1",
        "displayName" : "First Choice",
        "default" : "y",
        "entries" : { "x" : "1", "y" : "2", "z" : "3" }
    };

annotation { "Feature Type Name" : "My Feature" }
export const myFeature = defineFeature(function(context is Context, id is Id, definition is map)
    precondition
    {
        annotation { "Lookup table" : lookupTable }
        definition.p is LookupTablePath;
    }
    {
        // Define the function's action
    }, { /* default parameters */ });

If you can post a small code snippet where this is breaking here, I'll log a bug.

dave_cowden

weird. so with that sample, inside of an editing logic function, and inside of the body,

print( definition.p ) would give { "choice1" : 'y' } ?

for me in both cases, and before any user click, definition.p would be an empty set. I'll make see if i can make a simple document to repro-- may example is way too complex to post, so it coudl have a bug too.

ilya_baran

Ah, no -- I was just looking at the UI.  Logging a bug.

dave_cowden

Ok. as a side note, the hole feature in std. works around this-- somehow. The code was a bit too complex, i gave up trying to figure it out.

In my case, for now the workaround was to do something like this in the editingLogicFuntion:

var lookupPath = definition.path
if ( oldDefinition == {} ){
    lookupPath = lookupPath ( { 'choice': 'p' } )
}

this allowed me to continue as if it was populated as I expected. but of course this code is brittle because it is a duplicate of what's already in the lookup table.

ilya_baran

The hole feature regen doesn't look at the lookup table.  Only editing logic does and it only looks for changes to it -- and after the first change, the value passed in is correct.