That looks alright. Was it consistently doing the mm/dd/yyyy format if you pick other dates? How about the Browser Cache? Have you tried to clear that?
Can you double check on the DOM that the HTML rendered already has that option passed in? If you right click on that element on Chrome, and select “Inspect Element”, can you help verify that you can see this:
If not, then clearing the cache should help resolve that.
Otherwise, try to put it out of that patternfly directive(?) and check if it is still the same.
Yes. Inspecting shows tm1-date-option="{format:‘dd/MMM/yyyy’}" or any other content that I fill in. Regardless, the filed keeps showing the default format.
I’m in fact using Apliqo-UX. Applying the empty option “{}” , I get the format mm/dd/yyyy.
For now, what we’re doing is merge, in an HTML form, the tm1-ui-dbr form numbers and common text fields and uib-datepicker for dates. Then we pass the dates as parameters to a process.