how to check for empty parameter

Question

how to check for empty parameter

Ruben Verschueren 55

I'm making an azure workbook where I have a grid (data from an azure table) and some buttons to do CRUD like actions.

I've configured it so that when one or more rows are selected the parameter "rowkey" is updated with the rowkey values of the selected rows.

what I want to achieve:

use the rowkey value(s) in second query that calls a custom endpoint. I've added only one for the first action/button.
do not run the second query until a rowkey is selected AND an action/button clicked since there will be multiple options

issue:

checking that a parameter is empty doesn't seem to work consistently.
is this even the right way to set up a row selection -> POST to endpoint -> show result scenario?

I've set up these two buttons that save the selecteAction in a parameter (I later want to clear it again when an action is complete, so I can hide the buttons until the next row selection User's image

I've set up the conditional visibility but the buttons are always visible. I've tried testing for is not equal to

not set
null
"null" (and setting the param to "null" as default)
"" (empty string)
undefined

User's image

So either I'm missing something that may or may not be obvious, or it's a bug.

P.S: apologies for the wall of text....

Accepted answer

0 additional answers

Your answer

Answer 1

Alex Burlachenko 9,780

Ruben hi there, thanks for posting this, its a cool scenario u're working on.

in azure workbooks u gotta check empty params carefully. try using 'is empty' or 'equals' with an empty string ''. azure workbooks parameters. sometimes 'not set' acts weird, so test with simple empty string first.

also in ur conditional visibility, set the default param value to empty string '' right at the start. then use 'is not equal to' '' for the check. this usually works smoother than null checks.

when handling selections and actions, always reset the action param after u use it. like clear 'selectedaction' right after the endpoint call. this prevents ghost clicks and weird states.

ur endpoint call should have two conditions: rowkey exists AND action is clicked. chain these with 'and' in the query settings. makes the logic bulletproof. worth looking into how other tools handle this too. the pattern is similar selection >action >clear state. keeps things predictable ))

about those buttons staying visible, check the param names in visibility conditions. sometimes a typo sneaks in and the condition just skips silently. happens to the best of us :))

ur setup is actually pretty solid for crud in workbooks, just needs a tiny logic tweak. u got this %)

let me know if the empty check still acts up after trying these

rgds,

alex

Ruben Verschueren 55 Reputation points

2025-06-20T12:34:17.44+00:00

as I suspected the visibility of the buttons was an oversight. put in not set as text instead of just leaving it blank.

Thank you for the suggestions. I'll go over them all. good to hear I'm on the right track.
Alex Burlachenko 9,780 Reputation points

2025-06-20T12:36:31.0733333+00:00

yes u are on the right way, and u are welcome, keep posted me.

rgds,

Alex
Ruben Verschueren 55 Reputation points

2025-06-20T12:42:55.03+00:00

forgot one thing, how do I clear the parameter when the I get the response back from the query? I've only found the option to manipulate params when clicking on a row
Alex Burlachenko 9,780 Reputation points

2025-06-20T15:02:12.5966667+00:00

)))) in the Microsoft world, u can use the 'merge' transform in ur query step to reset params. right after ur endpoint call, add a new query that just returns an empty value and set it to update 'selectedaction'. workbooks transforms. its kinda hidden but works like magic :))

or try this hack, add a 'set parameter' action to ur success notification. when the query succeeds, it'll trigger the param clear. just make sure to set 'show as notification' in query settings first.

for any platform, always build a 'reset' button that clears all action states. users love it when they can start fresh. make it visible only when params have values.

also check this pattern, chain another query after ur main one that always runs and clears params. bit brute-force but never fails ) just set 'depends on' to ur main query and make it return empty. so.... like that

rgds,

Alex
Ruben Verschueren 55 Reputation points

2025-06-23T07:39:36.1933333+00:00

your second suggestion is what I'm looking for. the issue is I don't see a why to get that success notification or the 'show as notifcation' option. Are these perhaps only available for certain types of datasources?

here is my current custom endpoint action that is triggered when a row from the previous query is selected (sets "rowkey parameter) and the selectedAction parameter is set to "reprocess". the response is still a dummy that replies with the values of the input parameters for testing.

I only see the option to manipulate the parameters when a row in the result grid is clicked. That is not useful in my use case it should do it as soon as the response is received from the endpoint.

a reset button is another option, but that would require the user to click it. I could set it up so that you either see the action buttons or the reset button with conditional visibility. But if the user does not click reset, the previous selectedaction is still there and will call the endpoint when a new row is selected in the first query.

The data in the first query are actually service bus DLQ messages that I've stored in an azure table. the idea being that the user can select one (or more) and resend the message or delete it from the azure table. so I need to ensure you don't accidentally run either action without an explicit click.

thanks for the assistance. so far I've only made a few workbooks to display graphs etc. this is new to me.

Share via

how to check for empty parameter

0 additional answers

Your answer