Please make lookup-entity support expressions

Not planned

Follow

andreas.krutnes

• February 24, 2022 08:20

"lookup-entity" seems to not support expressions. We can't for instance access anything in _T.

Example:
["add", "tmpvalue", "mmm-meteringpointstatuses:707057500064711313_3"],
["add", "working_ex", ["lookup-entity", "mmm-meteringpointstatuses", "mmm-meteringpointstatuses:707057500064711313_3"]],
["add", "not_working_ex", ["lookup-entity", "mmm-meteringpointstatuses", "_T.tmpvalue"]],

0

• Official comment

  

  Geir Ove Grønmo

  • May 03, 2022 12:20

  I can confirm that "lookup-entity" does not support expressions currently. We did introduce that restriction on purpose as it was meant to be used to look up static entity data. This function does not support dependency tracking at all, so any changes to the entities that you look up won't trigger dependency tracking. Any changes to the lookup data means that the pipe must be reset to be consistent.
  
  It is fairly trivial to lift that restriction, so we'll discuss this internally once more to see if it makes sense to lift the restriction. As you seem to want to lookup data in "_T." that probably mean that you can use hops to solve the problem (since "_T." is derived from "_S.").

   

  Comment actions Permalink

Please sign in to leave a comment.