Capture error in a Card

andres · 2022-07-08T08:01:37+00:00

There was an error rendering this rich post.

We're currently using a Range Selector card to allow users to filter our data based on a MIN and MAX date. The problem is that we sometimes have no data when users initially access our platform and they see the error "Error: The maximum value is less than the minimum value" and that leads this to thing that there's an actual problem with our side (see the image below)

Apparently, the rest of the filter types throw no error when there's no data and I've not been able to find any settings in the card building section that allow me to rephrase the error or handle it better. Is there any way I could handle this?

Find more posts tagged with

Error

Accepted answers

All comments

MichelleH

@andres You can change what the users see if there is no data under Chart Properties - General - No Data Message. I'm not familiar with this particular error, though, so you will have to test this to see if it works

andres

Hi @MichelleH,

Thanks for the answer, but I already tried that with no luck. The default "No Data available" message appears on the rest of the cards and also on this one if I pick a different filter type.

MichelleH

@andres Can you please share some screenshots of your date filters?

andres

@MichelleH

Sure! For some reason I thought that I'd already included them at the top.

Working Example

The Filter Type that we're using

RobSomers

@andres Are you using the same date field for your Minimum Value and Maximum Value?

andres

@RobSomers yes, it's the same date field

MichelleH

@andres Is the date field a beast mode?

andres

@MichelleH No, it's a normal date field. Below you can find a couple of examples

Godiepi

@andres

Can you create a table card with 3 columns ? User, MIN(Date), Max(Date) then filter to the user or users that get the error to actually see what the MIN and MAX columns display? is because nulls , is it a generic date associated that is messing up ? etc ..

GrantSmith

@andres

I'd recommend logging a bug with Domo Support. That message shouldn't appear if there's no data. The No Data message should appear instead.