Date field value getting stored incorrect in the lead field

Date field value getting stored incorrect in the lead field

Issue: Date field value is getting stored incorrectly in the lead field, even when passing correctly from Lapp.
​
Explanation:
When User perform an activity an lapp will get triggered, and some predefined values get fetched and updated on the form.
Sometimes, when the Lapp pass date is 20-12-2030, but in the lead field, it was updated as 20-12-1930 incorrectly.



Solution: 
This issue is occurring due to a mismatch between the user’s date format and the format in which LAPP is sending the date.
The user date format is MM/DD/YY, while LAPP is sending the date in a different format, YYYY-MM-DD or YYYY-DD-MM.

Because of this mismatch, an issue occurs during mail merge when processing date field values.

To resolve this issue, ensure that both use the same date format, or enable the "Format mailmerge data" setting, which will format the data at forms level.
6f833bf0e5d247d5a09b3bc831cff62d

    • Related Articles

    • Date format is showing as yyyy-mm-dd where mail merge is used

      Issue reported: The Company profile employs a distinct date format, yet the mail merge displays dates in the yyyy-mm-dd format. Solution: This is the default behavior of the system since the values are stored in the backend database in the format ...

    • Filter and search only opportunity fields in form rules

      Problem: Currently if you try to search form rules containing a particular opportunity field in the search bar, it does not yield any results. This is a bug and will be fixed in upcoming releases. Workaround: Remove the opportunity code in the search ...

    • Lead Cohort Assignment | Gurnick and GEGI Integration

      Issue Raised: Leads not containing the right Cohort. Alternative/Associated Queries: 1) Leads in LSQ and Students in GEGI have different Cohort identifiers. 2) Registration Link is not being sent. 3) Lead is not updating in the as per GEGI data. ...

    • Field values not getting reflected on the Portal

      Issue Description: The values of a field updated on the form are not reflected in the portal. Reason: This is a caching issue. To fix it, we need to reconfigure the form in the portal and republish the portal. Example: We add a new value to a ...

    • How to hide the Lead Age from the Mobile App.

      Scenario: How to hide lead age from the Leadsquared mobile application. Solution: Steps to hide lead age: If you see in the Mobile App by default the lead age will be shown up against the leads, If the customer wants to remove the lead age then It is ...