Hi All, hope you all are doing great, I'm getting the following error:Error Evaluating UI Expression Expression evaluation error [evaluation ID = PNO05] in rule 'abs_clientsearchresponse2' (called by rule 'abs_clientsearchrequest2') : A null parameter has been passed.
When trying to invoke a process model inside a!gridColumn as follows:
a!gridColumn( label: "BUC", value: a!richTextDisplayField( label: fv!row.IDE_CLIENTE, value: a!richTextItem( text: fv!row.IDE_CLIENTE, link: a!startProcessLink( processModel: cons!ABS_CLIENT_REQUEST2_PM, processParameters: { buc: fv!row.IDE_CLIENTE } ), linkStyle: "STANDALONE", color: "NEGATIVE", size: "STANDARD", style: "STRONG" ) ), align: "CENTER" )
The rule: 'abs_clientsearchresponse2' is displaying the row without any error:
But when I click over the BUC link, the above error is displayed, the pv is declared as Parameter with the same name in the PM, I haven't been able to find the root cause of the error. Could you please help me?
Any help will be greatly appreciated.
Thanks and regards,
Jose Castellot
Discussion posts and replies are publicly visible
Hi All,
For those who have the same issue, here you go how I fixed it: a!gridColumn( label: "BUC", value: a!buttonArrayLayout( buttons: { a!buttonWidget( label: fv!row.IDE_CLIENTE, style: "LINK", size: "SMALL", color: "NEGATIVE", saveInto: a!startProcess( processModel: cons!ABS_CLIENT_REQUEST2_PM, processParameters: { buc: tostring(fv!row.IDE_CLIENTE) } ) ) } )
I see earlier you were using rich text and you're calling a!startprocesslink in link parameter, which was erroring.
In order to solve issue, you used button and in save into you called a!startprocess.Does it mean we cannot call a!startprocesslink in grid?
You can use a!startProcessLink with any link parameter anywhere. I think the root cause was something different.
Thanks Stefan Helzle Jose Castellot - Can you please post here what was the issue if you were able to find that?
Dhananjay Kumar said:Does it mean we cannot call a!startprocesslink in grid?
As stefan already mentioned, we most certainly can.
Personally I'm curious whether the OP's "toInteger()" call that was added in the second code snippet somehow made a difference (usually for a hard-typecast parameter, though, i'd expect it to be handled gracefully, but who knows whether this is some weird corner case).