-
Notifications
You must be signed in to change notification settings - Fork 3.6k
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]-[77]:Dissalowed Value DD.MM.YYYY in the Display Date Format Property of a Column in the Table Widget #18572
Comments
Assuming 10% of date users face this Stats
|
@vsvamsi1 please check this as well |
@dilippitchika These are the formats we can support |
@vsvamsi1 the same dd.mm.yyyy works in the datepicker widget but not here in the table, is there a reason? |
Hi @dilippitchika, Its very strange on the DatePicker there are no restrictions on the allowed in the formats. You could enter a random incorrect format like in the screenshot and there is no error from our app. For the datePicker it attempts to format what it can infer, whereas in the Table we limit it to a list. Im not sure what is the right behaviour. |
If we are the ones limiting to a list in datepickers inside tables, why can't we add DD.MM.YYYY? Regardind datepicker widget not validating, please create a separate issue |
Sure @dilippitchika will do that and these new formats we should support for Display date format and not Original Date format? |
We should support it for both i believe, display and original date |
We have another user on Discord who is trying to set the date format programmatically. The formats are supported in a Date Picker widget, but not in the Table Date column.
|
Another user raised the same issue on Discord. |
@ame-appsmith a workaround for this is to update the computed value and format it using moment |
#28784) #### PR fixes following issue(s) Fixes #18572 > if no issue exists, please create an issue and ask the maintainers about this first > > #### Media > A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video > > #### Type of change > Please delete options that are not relevant. - Bug fix (non-breaking change which fixes an issue) - New feature (non-breaking change which adds functionality) - Breaking change (fix or feature that would cause existing functionality to not work as expected) - Chore (housekeeping or task changes that don't impact user perception) - This change requires a documentation update > > > ## Testing > #### How Has This Been Tested? > Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration. > Delete anything that is not relevant - [ ] Manual - [ ] JUnit - [ ] Jest - [ ] Cypress > > #### Test Plan > Add Testsmith test cases links that relate to this PR > > #### Issues raised during DP testing > Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR) > > > ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
Is there an existing issue for this?
Description
A user is trying to use
DD.MM.YYYY
in the Display Date Format property of a table column, but it returns an error:Dissalowed value
.https://community.appsmith.com/t/cannot-set-dd-mm-yyyy-date-format-for-table-column/1694
Steps To Reproduce
users
sample database).DD.MM.YYYY
in the Display Date Format property.Public Sample App
No response
Issue video log
No response
Version
Appsmith v1.8.10-SNAPSHOT
Front conversations
The text was updated successfully, but these errors were encountered: