Controlling time field for an attribute

haripsv
haripsv Member
edited September 19, 2012 in Documentum #1

Hello Everyone,

We have a requirement to hide the time part of  a date field for a custom object type and just capture the date when the document is created.I have hidden the time field, but its still registering the default time(12:00:00) in the database.Is there a way we can prevent this from happening ? I want the value to be null.

Thanks

Hari

Tagged:

Best Answer

  • aflowers001
    aflowers001 Member
    edited September 19, 2012 #2 Answer ✓

    There is no way that I'm aware of. I assume you are storing the value in a DM_TIME and under the hood this is a date AND time value in the database. You could possibly look to store the value as a string and read/write from that, but the question would be why? If you logic dictates that the time is ignored just make sure that this requirement is carried through to the UI and other methods of viewing the data.

Answers

  • aflowers001
    aflowers001 Member
    edited September 19, 2012 #3 Answer ✓

    There is no way that I'm aware of. I assume you are storing the value in a DM_TIME and under the hood this is a date AND time value in the database. You could possibly look to store the value as a string and read/write from that, but the question would be why? If you logic dictates that the time is ignored just make sure that this requirement is carried through to the UI and other methods of viewing the data.

  • haripsv
    haripsv Member
    edited September 19, 2012 #4

    Hi Andy,

    Thanks for the reply. I guess the simple answer would be say NO to the client .The problem they have is they have reports from another system which doesnt have these time fields and when they do a comparison it looks odd with 12:00:00 defaulted to all the entries.

    Thanks

    Hari

  • DCTM_Guru
    DCTM_Guru Member
    edited September 19, 2012 #5

    "...when they do a comparison it looks odd with 12:00:00 defaulted to all the entries."

    - Then they (or you) need to do the comparison correctly.  If you are querying for documents based on specific date, use something like this:

    r_creation_date>=date('9/19/2012 00:00:00) AND r_creation_date<date('9/20/2012 00:00:00)

  • aflowers001
    aflowers001 Member
    edited September 19, 2012 #6 
    they have reports from another system which doesnt have these time fields and when they do a comparison it looks odd

    Is this comparing a report from the documentum metadata to another systems report? If so then just skip adding in the time to the documentum metadata report, some simple formatting should accomplish this

  • haripsv
    haripsv Member
    edited September 19, 2012 #7

    The report is just an excel sheet which a set a users use it to enter metadata when the document gets created.I dont know where the report is coming from.From the documentum side, we dont generate a report. People access the application to check the dates. I guess I should have been clearer when I stated comparing reports.

    Thanks

    Hari

  • haripsv
    haripsv Member
    edited September 19, 2012 #8

    Anyways thank you both for your input.Appreciate it.

Categories