What's the purpose of date picker "default date" if it doesn't reset to default date?

I asked this before (about a month ago) but still haven’t resolved the problem. Maybe I’m misunderstanding the phrase “default date”.

My app is a library app. Users can check out items, and the standard due date is 2 days from now.

So in creating a record of the borrowed item, I have a date picker field. I have the default date set to “2 days from now”. That way we don’t have to choose a due date every time.

But sometimes I need to choose a different due. date.

The problem is, whenever I pick a new date, that new date stays in the field, even if I exit out and restart the app.

I thought “default date” really meant default. I thought the default date would appear the next time I opened the screen. But it doesn’t seem to work that way.

Can someone please help? This is. very frustrating.

Keeping an eye on this one to see if there are any solutions.

@dilon_perera @Flawless @njimmy10

This may not be the solution you’re looking for… But here’s a workaround if you want to try using the “Markings Calendar” component and the “Randomizer” component from the marketplace. The markings calendar is currently $35 and the randomizer is free.

Remove the due date from the screen:

Add a randomizer for a UUID:

Set the marking calendar to create the rental with the default date 2 days from now. Then you can use the marking calendar to switch the due date.

Disable “click range end” and “enable click range start” so that users can select days after today and not before today:


What happens when clicking a different day:

1 Like

Thanks for that suggestion. That’s a lot! But I may give it a try.

Do you think my date picker issue is a bug, or is this how it’s supposed to work?

I’m not sure.

After a little testing, I can confirm that the date picker input does not re-set itself to the default value as the regular input component does.

This could be a bug or it could be that this type of input just doesn’t revert to the default setting.

FYI to anyone who is interested.

I filed a support ticket on this. I received a reply that says the team is aware of the issue and is working on a solution.

I appreciate that response. Hopefully it will be resolved soon.


This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.