Populate data by default into a grid

@erickp Please find attach the modified code. I hope this accomplishes your usecase.

queryEntity.txt

Put the if around the entire filter attribute. For example:
filter: if(isnull(ri!name), {}, a!queryFilter())

@erickp *attached. Apologies for the typo.

One more suggestion I would like to add here is, if possible, please make use of rule!APN_isBlank() instead of isnull. Just in case, if you aren't aware of rule!APN_isBlank(), please find attached the image. isnull might not work all the times, especially when you are working with a local variable in the SAIL interface.

Excellent thank you!

If you know that your search parameter will be a text string you can simply use isnull(trim(ri!name)) instead of the isBlank rule suggested above.

Hi,
I remember using APN_isBlank() when I was working on 7.7

Now, we are on 7.8 and I wont see that function available?

Do I've to download anything related for this function to be available?

Any inputs?

APN_isBlank is a rule included in the Common Objects application

forum.appian.com/.../summary

I suppose null or blank ({}) filters are not allowed instead use logicalExpression logicalExpression: if(
isnull(
ri!name
),
null(),
a!queryLogicalExpression(
operator: "AND",
filters: a!queryFilter(
field: "univ_name",
operator: "includes",
value: ri!name
)
)
)

@prernas Hi, whatever you have said completely depends on the scenario. If you have only one filter and just making use of the 'filter' argument without making use of the 'logicalExpression' argument, then definitely null values are allowed. For instance, the code snippet which I have uploaded above after making a correction or comment made by @jacobc thereafter is an perfect example for it and the user is happy with it as well. The same is explained at https://forum.appian.com/suite/help/16.1/Appian_Data_Types.html#Query as follows: "This optional field determines the filtration to apply to the query." This obviously states that 'logicalExpression' or 'filter' or 'search' argument is completely optional.

The comments made by you makes perfect sense when the 'logicalExpression' argument is used, which is generally used in case of multiple filters. Off-course even this way can also be used in the example here but we should also bear in mind that there isn't a problem with defining the null value for the 'filter' argument.

And to make the conclusion simple - you are defining the 'logicalExpression' as null when the filters aren't present. In the same way, the 'filter' argument can be defined as null if the filter we need to pass is null.

@sikhivahans You are correct. I had stated the example for multiple filters. If in case there is only one filter , 'filter' option can be used as filter:null()