Out of the box domain based attributes allow date format to be set to mm/dd/yyyy format like below
However a simple custom domain based attribute does have only mm/dd/yy as an option on reports as well as in the domain designer.
This limits the use of date formatting as PPM in our case is set to mm/dd/yyyy and that is what users want to see.
This is simple date selected using sql "Select datefiled from table" so no formatting is done at the source.
If we use to_char to format dates then the fields will be treated as text and hence dates will not be sorted as they should(uses alphabetical sorting instead of date sort)
What should be done to get everything showing mm/dd/yyyy format?
Also note that we have set the jasperserver default date format to mm/dd/yyyy and it only works for OTB domains,why?
This is normal behavior, all the OOTB domains' business dates have been manually modified to a different datatype, java.util.Date.
This was done not only for format purposes but also to ensure proper timezone handling.
When you create your own domain this doesn't happen. To workaround this, please try the following:
Important! Do not set any system dates, only the business dates in CA PPM. Internal dates should remain as timestamp. (Example dw_updated_date should be a timestamp)
This should work, please try it out and let me know.
Hope this helps -Nika
Awesome, will give it a try.
We could not import the modified domain as it said the underlying fields were used in some adhoc views. Now we have created a different version of the domain. Is there a way to import or migrate the adhoc views instead of asking users to recreate the adhoc views?
Learning: Dateformat should have been set while installing Jaspersoft.
We are on PPM 14.2 patch 6 and this change has brought up additional issue on the surface.
Below is result of this change along with the known bug that skews date filter on hitting apply.