Date Range Component Could be better

The "Date Range" component could be improved. i.e. This thing could start as early as 1970 and the only way the year can be advanced (without code) is by scrolling through the calendar which could take hours.

The "Date" component has a feature whereby you can click on the Year and change it, which solves this problem.

So I have used a Start Calendar and an End Calendar which works fine but I think this should be added to the "To Do" list for our component developers.

I am including a screen capture of the Date component.


I agree. :wave:

I agree @mdsmith1 the range component lacks the ability to quickly change the year or month by large increments. And yet it otherwise looks almost identical to the date picker component.

I think for the purposes of standardising (and improving) the UI component library, the dev team should consider this.


I think a number of the components need a second look.

The button, text, text input, number input and others have no style options for font size. We have colors, borders and rounded corners but no control of font size.

I think someone should look at this.


Mike, don't get me started!

The properties available on components are so arbitrary and frustrating. I can't even change the font look on a link component, let alone use markdown with it.

Retool: you can change these things in CSS
Me: Why should I have to? I could do this with Delphi 20 years ago.


Hey @stewart.anstey, I feel you. :sweat_smile:

Thanks everyone for the feedback! I've shared this internally as well! Hopefully, we can ship font size controls (among some of our other styling updates):crossed_fingers: as well as a date range upgrade

1 Like

Thank you @Tess!

Any ETA on the date range changes ? Being able to scroll by month only makes the component pretty useless considering the alternative (2 date components)

Hi @yiga2 Unfortunately, no update yet :disappointed: I'll let the team know you checked in!

1 Like

It try to implement my own datepicker as custom-component but this will not working:

  @import url('');
  html { font-family: 'Inter', sans-serif; }
  @supports (font-variation-settings: normal) {
    html { font-family: 'Inter var', sans-serif; }

  * {
    font-family: 'Inter', sans-serif;

  body {
    margin: 0;

  #react {
    height: 100%;
    width: 100%;

<script crossorigin src=""></script>
<script crossorigin src=""></script>

<script src=""></script>
<link rel="stylesheet" href=""></script>
<script src=""></script>

<div id="react"></div>

<script type="text/babel">
  console.log('foo', window.antd.DatePicker);

  const DatePicker = window['antd']['DatePicker'];
  const { RangePicker } = DatePicker;

  const MyCustomComponent = ({ triggerQuery, model, modelUpdate }) => (
     <RangePicker />

  // This is the entrypoint for the React component.
  const ConnectedComponent = Retool.connectReactComponent(MyCustomComponent)
  const container = document.getElementById('react')
  const root = ReactDOM.createRoot(container)
  root.render(<ConnectedComponent />)

But this Code freezes the complete retool!
What i do wrong here?

This is the same code withoutout the retool context:

This work as expected!

i found the error by myself.
it was this css from the Example:

  #react {
    height: 100%;
    width: 100%;

But my idea was nonsence because of the IFrame.
The Picker popup was trapped inside

There are still some open requests here, but we did ship font size in the Styles section