Got a weird issue here with IDC.
I have a vendor whose invoices are always dated dd-mmm-yy (like 14-Apr-25). I do have a DateFormat misc parameter set up for different formats that appear.
For some reason, dates with a two-digit day are accepted, but single digit isn’t (so 22-Apr-25 is fine, but 3-Apr-25 is not).
Has anyone come across this problem? Screenshots included:
Doesn’t work:
works:
When I tested this, I found that this format works with the DD-MMM-YY format in the Misc parameter. Your batch type locale may be causing a conflict with the date format.
I have a Misc parameter set up for it already though:
Don’t misc parameters overwrite Locale settings?
Edit: bit more info. My date locale settings are set to Canada and mm/dd/yyyy format. I have MANY vendor-specific DFDs with different DateFormats (mainly dd/mm/yyyy). It is ONLY this format and only with single-digit days.
My other dateformats work fine
DD-MMM-YY - I would use this format in the Misc Parameter and see if that resolves it.
My batch is using en-Us locale, the possible issue could be the locale and you can set that on the misc parameter to resolve date format issues.
My locale was set to en_CA as Primary, and en_US as Secondary. Anyway i changed it to US primary only, and it still has no effect.
On yours do you have the date format set to anything specific?
I have it as MM/dd/yyyy because that’s how the customer needs it. My understanding was that the DateFormat parameter allows for exceptions to this and enables the ‘translation’ of the date to MM/dd/yyyy?
The secondary locale does not work on the date formats.
These are the settings I have in use.
I haven’t done anything with the Date Display format other than keep as Original.
What version of IDC? Is this on-prem or cloud? What is the format of the InvoiceDate field?
This is how I tackled that issue.
I remember reading this post and trying to get that working for me. Then i found out about DateFormat and it solved my issue except for this one problem.
Time to revisit this maybe, thanks!
I’d test if the display format caused this issue. I’d maybe look at the date field and see if there is a format that would fix it.
