You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the Script Editor in Frappe Insights to create a query, columns with date values are being inferred as strings instead of the Date type. This creates discrepancies and limits the ability to perform date-related operations. Additionally, integer and other types are correctly inferred, which makes this behavior inconsistent.
Steps to Reproduce:
Open the Script Editor in Frappe Insights.
Use the following Python script to generate results:
results= [
{
"employee_id": 101, # Integer"salary": '2023-01-23', # String value (looks like a date but is a string)"join_date": frappe.utils.getdate(frappe.utils.today()), # Actual date value
}
]
Execute the script and check the inferred types of the columns:
employee_id: Correctly inferred as Integer.
salary: Correctly inferred as String.
join_date: Incorrectly inferred as String instead of Date.
Expected Behavior:
Columns containing actual date values (e.g., join_date) should be inferred as Date or Datetime types, depending on their structure.
Observed Behavior:
The join_date column is inferred as a String type.
Issue Description:
When using the Script Editor in Frappe Insights to create a query, columns with date values are being inferred as strings instead of the
Date
type. This creates discrepancies and limits the ability to perform date-related operations. Additionally, integer and other types are correctly inferred, which makes this behavior inconsistent.Steps to Reproduce:
employee_id
: Correctly inferred asInteger
.salary
: Correctly inferred asString
.join_date
: Incorrectly inferred asString
instead ofDate
.Expected Behavior:
join_date
) should be inferred asDate
orDatetime
types, depending on their structure.Observed Behavior:
join_date
column is inferred as aString
type.Screenshot:
@nextchamp-saqib
The text was updated successfully, but these errors were encountered: