issue with reject(fn!isnull, 'array of arrays') function on a data generated from an expression rule

RE: issue with reject(fn!isnull, 'array of arrays') function on a data generated from an expression rule

ManuelHTG — Thu, 03 Jan 2019 10:44:09 GMT

Thanks for the Idea, but it is not the right solution. For reaching that solution the best would be to use touniformstring() and then the reject function. The problem there is that then I get a flat array, which does not work for the graphical representation of the pie chart.

Rather than having and Index, the solution was to make it a datasubset.

Thanks for the suggestion.

RE: issue with reject(fn!isnull, 'array of arrays') function on a data generated from an expression rule

ManuelHTG — Thu, 03 Jan 2019 10:40:10 GMT

Thank you very much, that way worked for the reject function!

first I store on a local variable and call: local!aux.data

Then I get:

{null, null, null, null, null, null, null, null, {name: "Outbound", count: 1}, null, {name: "Mudcakes", count: 2}, {name: "Happy Industries", count: 2}, null, null}

Now I can call reject() : reject(fn!isnull,local!aux.data)

And then I get:

{{name: "Outbound", count: 1}, {name: "Mudcakes", count: 2}, {name: "Happy Industries", count: 2}}

So the pie chart looks as I wanted to:

Thank you!

RE: issue with reject(fn!isnull, 'array of arrays') function on a data generated from an expression rule

Jose Cavazos — Wed, 02 Jan 2019 22:09:54 GMT

Hi Manuel,

What i would suggest it may not be the best answer, Have you tried adding key value to the array of elements?
Find the following example.
reject(fn!isnull,
{
{}, {}, {}, {}, {}, {}, {}, {}, {
item:"Outbound",
id: 2
}, {}, {
item:"Mudcakes",
id: 2
}, {
item:"Industries",
id: 2
}, {}, {}
}
)

This will give you the output you need.

You can even test how the values are getting passed by using the a!foreach()
So if you do
a!foreach(
items: Your array,
expression:
fv!item)

This will remove the blanks by default and will give you {"Outbound", 1, "Mudcakes", 2, "Happy Industries", 2}.
If you use keypaired values will give your desired output also.

The issue is because it treats them as different elements even if they come within an array of arrays it counts them as separate elements if they don't come within key paired values.

Hope this helps. I'm sure you can get better suggestions on your problem.

RE: issue with reject(fn!isnull, 'array of arrays') function on a data generated from an expression rule

Mike Schmitt — Wed, 02 Jan 2019 21:59:52 GMT

It appears that Reject is flattening the resulting array prior to evaluating. This isn't much of a surprise to me, since Appian's ability to handle array-of-arrays in most cases is pretty spotty (and slightly unpredictable). I would suggest you consider making your expression rule pass back dictionary data instead of {text, integer} arrays, because then you could pretty easily weed out blank/empty entries from your return list without needing to bend over backwards to avoid the array flattening that's happening here.