How to properly use: setFeatureComputedParameter()

john_mcclary

What am I missing?
This is all the info I see in the documentation

I've tried many times, but I cannot get the feature name to stick like I've seen in measureValue.fs and variable.fs

MBartlett21

@john_mcclary
The parameter name has to be in the precondition for setFeatureComputedParameter to work.
PS: You don't have to use setFeatureComputedParameter to use # syntax in the feature name. You can just directly use #Name.

kevin_o_toole_1

FYI, in order to use #someValue in templates, you need either definition.someValue to be a parameter or setFeatureComputedParameter("someValue", ...). No need for both, but setFeatureComputedParameter is still useful for computed values that aren't inputs.

And yes, an individual feature's name and template are assigned when the feature is created, so if you're debugging this stuff and changing the feature name or template, you need to delete and recreate the feature in order to see the new name or template take effect.

MBartlett21

@john_mcclary
The parameter name has to be in the precondition for setFeatureComputedParameter to work.
PS: You don't have to use setFeatureComputedParameter to use # syntax in the feature name. You can just directly use #Name.

john_mcclary

Ok, so you also need to delete the feature and re-create it.
I was running in circles expecting the feature tree to update just by editing the feature.

Good to know you don't need setFeatureComputedParameter

kevin_o_toole_1

FYI, in order to use #someValue in templates, you need either definition.someValue to be a parameter or setFeatureComputedParameter("someValue", ...). No need for both, but setFeatureComputedParameter is still useful for computed values that aren't inputs.

And yes, an individual feature's name and template are assigned when the feature is created, so if you're debugging this stuff and changing the feature name or template, you need to delete and recreate the feature in order to see the new name or template take effect.