Skip to content
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

Datefield formatting (DD-MM-YYYY) data doesn't match endpoint data/what has been selected #1166

Closed
hlayisanimazuze opened this issue Mar 12, 2024 · 0 comments
Assignees
Labels
bug Something isn't working ready for testing

Comments

@hlayisanimazuze
Copy link
Collaborator

hlayisanimazuze commented Mar 12, 2024

If this DD-MM-YYYY formatting is used on the table dateField display component, details view dateField component and entity configuration(details only), it display data that does not match what the endpoint has. This issue occurs when
using the following:

  • Inline adding and display dateField component
  • Details view updating the formatting property on the dateField and create
  • When the formatting is applied on the entity configuration, the details view still displays the wrong data than what's received from the endpoint

Steps to reproduce the behavior adding:

  1. Go to 'https://function-adminportal-test.shesha.dev/dynamic/TestModule/testTable-member'
  2. Click on 'membership Start Date' and select a date
  3. Actual Results: The displayed date does not match what is being selected

Steps to reproduce the behavior displaying:

  1. Go to 'https://function-adminportal-test.shesha.dev/dynamic/TestModule/testTable-member'
  2. Search for conversation booster
  3. Check membershipState date column and compare with that data from the endpoint
  4. Actual Results: Both values do not match

Steps to reproduce the behavior details view: (This also applies when the formatting is applied on entity configuration)

  1. Go to 'https://function-adminportal-test.shesha.dev/dynamic/TestModule/testBlank-member?id=4d5e9904-f65b-402f-982e-7b7370854a9c'
  2. Check membershipState date column and compare with that data from the endpoint/Edit the component and select a new value
  3. Actual Results: Both values do not match

Expected behavior

  1. When the formatting is applied on all the above mentioned use cases, the formatting should not change the data but display what is received from the endpoint
image
@hlayisanimazuze hlayisanimazuze added the bug Something isn't working label Mar 12, 2024
@hlayisanimazuze hlayisanimazuze added this to the Backlog milestone Mar 12, 2024
@hlayisanimazuze hlayisanimazuze changed the title Datefield formatting (DD-MM-YYYY) data doesn't match endpoint data Datefield formatting (DD-MM-YYYY) data doesn't match endpoint data/what has been selected Mar 12, 2024
AlexStepantsov added a commit that referenced this issue May 20, 2024
…differs to what the backend is expecting #1468

Datefield formatting (DD-MM-YYYY) data doesn't match endpoint data/what has been selected #1166
AlexStepantsov added a commit that referenced this issue May 20, 2024
…load bug #1543

Dyanamic dateField filtering sends the incorrect format expected by the endpoint bug #1542
Date not selectable during inline editing when show time property is enabled bug urgent #1541
The payload sends the exact format received from the component which differs to what the backend is expecting bug urgent #1468
Datefield formatting (DD-MM-YYYY) data doesn't match endpoint data/what has been selected bug #1166
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ready for testing
Projects
None yet
Development

No branches or pull requests

3 participants