I’ve got an interesting issue going on with updateable dashboards, date fields and time zones (I think). This is on 10.2, classic dashboard, on-prem.
So, I’ve got a fairly simple updateable dashboard, the BAQ is against OrderHed, OrderDtl, OrderRel and Customer. The only updateable field is a UD field on OrderRel. The dashboard has typical search criteria (customer ID, Order Number, PO Number), and displays among other data the OrderRel.NeedByDate and OrderRel.ReqDate. I’ve got a custom button in the tracker view where the user can enter a value into a control there, and the custom button just loops through the epiDataView and sets the UD field to that value (meaning they can update an order of 20 releases with one click rather than having to update each release.
So, here’s the issue. The server running this is in the Eastern Time Zone. When a user who is on a computer in the Central Time Zone runs this, when they click the button to update the UD field, the NeedByDate and ReqDate in the grid view “back up a day”. Then they click SAVE to update the changes, and the NeedByDate and ReqDate go back to their regular values. This doesn’t happen to people in the Eastern Time Zone.
I should stress again that the NeedByDate and ReqDate are NOT updateable fields in the dashboard. And the button logic to set the UD fields on the records just loops through the dataset and sets ONLY the OrderRel UD Field.
Anyone else experience this?