Skip to main content
A
AP_958723617-Peridot
17-Peridot
June 15, 2021
Solved

Events as an input

  • June 15, 2021
  • 2 replies
  • 3476 views

The selected rows datas are taking time to pass input to expression/validator than events. Shall we pass Event as a input to expression/validator? Is that a good practice??

Best answer by abjain

@AP_9587236 : Yes these properties are not of type events. So these can be bound as input parameter to expressions and is fine.

2 replies

A
abjain15-Moonstone
15-Moonstone
June 15, 2021

@AP_9587236 : Can you please explain the use case here on what you are trying to achieve ? I don't think that binding events to expression parameters is possible but if you can explain clearly it would be helpful. If possible , please share some screenshots too.

A
AP_958723617-PeridotAuthor
17-Peridot
June 16, 2021

Once the All Data of infotable values passed to Collection widget from service, we will get the options like Event:SNo, Event:Name,... as I highlighted in the below attachment for your reference. Binding those values to the "inputs of" expression/validator is efficient or not?

P
PaiChung22-Sapphire I
22-Sapphire I
June 15, 2021

Not quite sure what your question is or what you are trying to do.

But you can't 'pass events' you can use events to trigger.

So if you use selected rows, you can use selected row changed to fire the evaluation

A
AP_958723617-PeridotAuthor
17-Peridot
June 16, 2021

Once the AllData of infotable values passed to Collection widget from service, we will get the options like Event:SNo, Event:Name,... as I highlighted in the below attachment for your reference. Binding those values to the "inputs of" expression/validator is efficient or not?

P
PaiChung22-Sapphire I
22-Sapphire I
June 16, 2021

Are you specifically referring to the Collection widget passing back selected row information?

I'm not certain but there might be a bug within that context.

Please search support.ptc.com for that

Terms & ConditionsCookie settingsAccessibility statement