Skip to main content
Jun 15, 2021 9:21 AM UTC
Solved

Events as an input

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??

abjainAnswer
Jun 16, 2021 5:33 AM UTC

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

11 replies

Jun 15, 2021 12:49 PM UTC

@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.

Jun 16, 2021 5:10 AM UTC

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?

Jun 15, 2021 8:35 PM UTC

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

Jun 16, 2021 5:11 AM UTC

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?

abjainAnswer
Jun 16, 2021 5:33 AM UTC

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