Extra Text error when parsing date/time in version 2023.9.9

🧩 Low-Code Development Workflows
#1

A workflow that had been working prior to upgrading to version 2023.9.9 is now throwing a new error. A record update was failing, so I decided to insert a prompt to see what the data looked like. This is what I got:

image
image1716×564 37.8 KB

Any idea why this is happening? The time/date doesn’t look any different, but for some reason the time portion is now considered “extra text” and is invalidating the input.

#2

Can you try pulling the image and trying again, there was an update after the initial release.
If it’s still happening, please provide:

  • The field types, you’re working with and their configurations
  • The expression that is causing the issue
#3

I pulled the 2024.9.0 image, checked all the permissions, but the problem is still there.

Here are the particulars:

record (composerecord) (module: memberposition)
Field: record.values.memberPositionEffectiveDate (DateTime), configured as Date Only

oldAssignmentRecord (composerecord) (module: memberposition)
Field: oldAssignmentRecord.values.memberPositionRemovedDate (DateTime), configured as Date Only

Expression:
oldAssignmentRecord.values.memberPositionRemovedDate (DateTime) = record.values.memberPositionEffectiveDate

Attempting to set oldAssignmentRecord.values.memberPositionRemovedDate equal to record.values.memberPositionEffectiveDate causes the workflow to stop (no error message shown) when attempting to update oldAssignmentRecord. Attempting to display the data in a non-blocking message prompt gave the error shown above.

Inspection of the action log showed this message when running without the non-blocking message prompt trying to display the data:

image
image1176×292 23.2 KB

#4

Is there a way you can check on the 2023.9.9 version?
I’ll try to replicate it. What is your DB?

Also the types in the expression are important. And the trigger configuration

#5

2023.9.9 is doing the same thing. Also, for some reason, the system seems to think that there is a value in an empty date field, and that is causing problems.

#6

@colby.ritter
Which version were you using before upgrading to version 2023.9.9?
Or, if you were already on 2023.9.9, under which tag?

Additionally, it would help us reproduce the issue if you could share the exact value of memberPositionRemovedDate (DateTime) as it appears in the database.
If possible, sharing a screenshot of your workflow expression would also be helpful.