Ok, I have a dataview for a BAQ. Got the grid setup via guided setup.
Trying to use the provider model for easier refresh. (I’m using pub/sub)
The field I am trying to update is a date field. It will not even show the datetime editor.
It works fine for text fields.
If I don’t set a BAQ in the provider model, and populate the dv manually, the editor shows up and works fine.
I’m assuming this is a bug with no workaround, but throwing it out there.
Have you tried defining the editor model directly?
Go to your grid and go Grid Model > Columns and on your column set the ERP Editor Model to datetime
Yes, no change.
Was gonna suggest the same per:
The plot thickens. Added a Calculated DateTime Field and it works correctly.
Weird, I just tried to create a quick dashboard with a uBAQ that updated OrderRel.ReqDate using standard BO update and it worked fine.
Same, created a simple Ubaq to update startdate on jobhead. the editor shows the datepicker.
Is the common editor selected in the advanced column editor configuration of the BAQ?
Also, try collapsing the panel and reexpanding it? I have had this problem before with it not loading a dropdown initally when it launches… no satisfactory solution so far.
At first I didn’t get the question as I still mostly use Classic BAQ. But I checked it in Kinetic and it’s set to Date Picker which must be default as it’s called “Common Editor” in Classic.
Yes.
nope
This only occurs if I let the provider model refresh the baq.
What’s weird, a calculated datetime or date works fine.
I inspected the json, and didn’t see anything weird.
I just made a new one, super simple and it worked.
WTF.
New what? New Grid? New BAQ? New Dashboard?
New baq, new db
Pretty standard application studio
Curious what Format value in GetQueryResultSetMetadataByID response just before ExecuteBaq request. Wonder whether there was a diff between date field and calculated date field.
Seems likley from where default column types are inferred.
{date} in the one that works and the one that doesn’t.
Same for the calculated field that works regardless.
More weirdness. The field I was using, was brought up from a subquery.
If I linked and got a field from an actual table, it worked again.
What a POS.
Column inheritance is quite a mess. Hoping they go back to the drawing board on the grid component.
That wish applies to so much of Kinetic.
