Defect? unremovable "Empty Value" value appearing in the spec for a new report and blocking me from proceeding

[Berto2002]

I just tried to create a report using the "value is like" filters in a standard Entity Report on the Request table and this "Empty Value" pops-up. It cannot be removed. Clicking it and clicking "delete selected value" does nothing.

 

It also appears when we use the "is one of these" filter. For these, we can add a new value which then relegates the "empty value" box to a small grey lozenge (below) and we can select and delete that but the resulting search/filter doesn't seem to work.

So at the moment, we are stuck and cannot create a new report with filter on the Request table; pretty basic stuff.

Anyone else got this? I will report to Premier Support if not updates from the community.

[James Ainsworth]

Hi @Berto2002

Thanks for your post.

I believe that I have replicated what you are experiencing.  The development team will investigate further to confirm if there is an issue.

[James Ainsworth]

Hi @Berto2002

I've looked at this again, and I have found that the <Empty Value> or in the second case, the blank entry can be double-clicked to change value.  Or, if unwanted, it can be selected and then deleted.  Hopefully this should allow you to continue with defining your report.  The remaining aspect is just to find out if there is a reason for the <Empty Valuce> being added when you first add the criteria to the filter.   I'm assuming that the default <Empty Value> may have been added to prevent issues with incomplete filters.

[Berto2002]

Oh wow, what service. Yes, the double-click does enable me to edit it. OK thank you for looking into the behaviour here. It's not intuitive to have the delete value button not working.

[James Ainsworth]

I believe that the Delete value button will work, but only once you have more than one value.  The delete button is not enabled when there is only one value so that it won't leave the criteria in a position where it has no value associated to it.

[Gerry]

@Berto2002

We found that there was a problem in our API serializer that was not correctly handling empty string values in an array that sits within a choice type.  It turned out we did not have a test case for this particular scenario so missed it.  This has now been fixed so the XML/JSON structures will no longer be broken.   We will do some testing in the UI to make sure this is also consistent, should all be live in the next few days. 

Gerry