Date Range Fieldtype (Reference List)
Description
Environment
Attachments
relates to
Activity
Peter Takacs November 24, 2022 at 9:24 AM
“AFAIK, the text box shows the effective date range, for e.g “01-01-2022 - 01/31/2022”, i.e just a duplicate of what’s in the 2 date editor input.“
Yes, you are correct, the only exceptions are Before, After and On, so e.g. the text box shows “Before 01/31/2022” to avoid confusing strings like “- 01/31/2022”

Heng Sin Low November 24, 2022 at 3:45 AM
hi ,
“They said they have the code to sync the textbox with the dates, isn’t it?”
AFAIK, the text box shows the effective date range, for e.g “01-01-2022 - 01/31/2022”, i.e just a duplicate of what’s in the 2 date editor input. , correct me if I’m wrong here.
Peter Takacs November 17, 2022 at 12:07 PM
the component is just partially usable on mobile, so we kind of lose the ability to run reports and processes on mobile phones
Created a new ticket for this issue
Carlos Ruiz November 17, 2022 at 10:50 AM
Having both textbox and date editor visible in a multiline layout will create another issue - since the date editor is editable, you can have inconsistency between the 2 date editor and the textbox.I think if you want the 2 date editor to be visible, what we have implemented now for infowindow, etc is good enough for me.
They said they have the code to sync the textbox with the dates, isn’t it?

Heng Sin Low November 16, 2022 at 11:30 AM
Having both textbox and date editor visible in a multiline layout will create another issue - since the date editor is editable, you can have inconsistency between the 2 date editor and the textbox.
I think if you want the 2 date editor to be visible, what we have implemented now for infowindow, etc is good enough for me.
Carlos Ruiz November 14, 2022 at 11:45 AM
Hi team,
I have several concerns about the new component:
Is not possible to enter the date range using keyboard
the component is just partially usable on mobile, so we kind of lose the ability to run reports and processes on mobile phones
what I see is the component is not responsive and doesn’t accommodate when changing options, for example in Trial Balance:
changing from the default to Between the apply button and the second calendar are not visible, it seems to appear after you click out and open it again
changing from the default to Before the apply button is not visible
Quick is not usable at all because the apply button is not visible
I don’t know why (probably a bug) - but opening the Trial Balance is showing Current Month in the textbox, when there are not defaults in the account date field
This lead me to see, that the “Current Month” message is not enough, it forces the user to do mental calculations to know which dates are included in the range - even worst with a default for example like “Previous 4 Months”, so that reconfirms my suggestion to show the dates next to the textbox
So, I stick to my suggestion of having the component with the dates, which could be entered manually, and the textbox that translate the range into something readable. IMO we don’t need the flag/switch.
Heng Sin’s concern is probably about the component being responsive, as I propose it is maybe too wide for small screens, but I guess it can be made responsive, or multi-line.
Regards,
Carlos Ruiz
Peter Takacs November 14, 2022 at 9:56 AM
Hi ,
I want to provide a little recapitulation:
In the latest commit I've removed the new Reference, since we agreed that the implementation doesn't follow the existing convention, so we won’t need that anymore.
Current state as POC: the new editor is shown by default in Process Parameters when a date parameter is range (replaces the 2 date editors).
Probably 2 main questions remain:
Should we make some sort of switch (e.g. an additional checkbox or list field as suggested below), or simply replace the current 2 date editors with the new DateRangeEditor (as it works currently in the PR)?
Should we improve the design or is the current design OK as first version?
After these are answered, then the DateRangeEditor can be implemented to other places (FindWindow, InfoWindow) probably still in the scope of this ticket - for now we use it in process parameters to test and clarify the concept

Heng Sin Low November 11, 2022 at 1:04 PM
Layout wise, should works better in multiline. However, as it is, it wouldn’t looks good with what’s in the current PR.
Carlos Ruiz November 11, 2022 at 10:02 AM
Would it work better if done multiline?

Heng Sin Low November 10, 2022 at 10:08 PM
That looks too busy for me and it is probably too wide to fit in nicely.
Carlos Ruiz November 10, 2022 at 3:53 PM
Hi team [ ]
Thinking futuristic - the implementation of relative date search in will require definitely a textbox, and probably the date fields won’t be shown or they can be shown just as a reference for the user.
So, my thinking is - instead of making a toggle option as proposed by Peter, maybe we simply make the display showing the textbox, the button and the two dates, something like this:
My thinking is - with relative search - we are probably going to need this textbox as editable, and when the user enter some “formula” the dates are calculated.
So - this textbox doesn’t need to be optional, it can be always there, and we get used to that, at this moment readonly, on all the date ranges in processes, find and info windows.
In future with relative search, the textbox will probably be editable and when the user enters a “formula” the dates are calculated, I think we are going to need a way to “save” that formula - for example to define it as default, or to keep it in a “saved search”.
So, summarizing, I would suggest to change the Date Range Picker editor to show something as the image above, no need for the legacy/new flag.
WDYT?
Regards,
Carlos Ruiz
The purpose of the development is to introduce a new Date Range field type using Date Range Component
Setup: in application dictionary select new reference on Date column (window field, info window, etc.)
Main changes/attributes
User instead 2 fields the user interact with Date Range Component
The field display human readable range eg. Previous 2 months
example screenshot