cancel
Showing results for 
Search instead for 
Did you mean: 

"Value is invalid" when searching for a date

Former Member
0 Kudos

Hi!

I added some property metadata fields to one of our KM folders storing contracts. So each document stored inside this folder has additional properties like "type of contract", "day contract was signed", etc.

Since we also want to search using those criterias (eg. "find all contracts signed after 12/01/2005"), I added those properties to the drop-down field in the search dialogue (under "predefined properties").

This is working fine, the properties are included in the drop-down list. Most of them are only "string" properties like "signee" etc., and there is no problem using those for filtering.

But there is a problem with the properties containing a date, like "day contract was signed". Naturally those are of the type "date", which I explicitly set in the options. The UI is adjusting to this data type when choosing this property in the search dialogue: A calendar symbol appears right after the input field where one can choose a date, and the date one chooses is filled in correctly. However, the search dialogue won't accept it upon clicking "Search". The message "Value is invalid" appears and the usual red box appears around the date indicating invalid content.

It's interesting that this does not happen when I set the data type of this property to "timestamp" (where there is an additional "time" value stored along with the date). When doing so, the search dialogue accepts any date I choose and all works fine.

I would go along with the "timestamp" datatype and avoid this issue, but we really do not need the time information in this case, and it's only adding unnecessary data to the already laden folder listings.

Is this a bug? Can anyone confirm this? Or did I miss something?

Thanks a lot in advance for your input,

Jens

Accepted Solutions (0)

Answers (2)

Answers (2)

detlev_beutner
Active Contributor
0 Kudos

Hi Jens, hi Matthias,

wow :neutral_face:

I'm just in a project where this will occur (we have just not tested this case). So it's really urgent to get this fixed for me (our customer), too.

Would anyone be so kind to update this thread when new information comes up?! In this case I wouldn't have to raise an own OSS message... (otherwise I definitely would have to...).

Thanks in advance

Detlev

Former Member
0 Kudos

Detlev;

I'll post it here as soon as I hear anything useful. I believe our Systems Engineering department placed the call last Friday and I'm being informed on a daily basis about the progress.

I'm afraid SAP is a bit on the slow side at the moment. We are currently waiting for answers to several OSS messages that haven't been updated since we placed them over a week ago.

Bye,

Jens

D021954
Employee
0 Kudos

Hi Jens and Detlev,

issue will be fixed with:

NW04 SP 14 Patch 4

and

NW04 SP 15 Patch 1

and all higher versions.

Regards Matthias Röbig-Landau

detlev_beutner
Active Contributor
0 Kudos

Hi Matthias,

thanks for the information!

Have a nice time

Detlev

D021954
Employee
Employee
0 Kudos

Hi Jens,

this is a bug.

Please provide an OSS message so that we can keep you on track when the issue will be fixed.

Sorry and regards Matthias Röbig-Landau