Skip to Content

Live Office 4.2 - date conditions, the struggle continues

We've experienced issues with date conditions in Live Office queries with every new update. I've documented some of these on the SAP community page in the past:

After upgrading to version 4.2 SP3, it seems the tool still isn't able to properly handle date conditions.
I did notice some improvement, however. With patch 6 we no longer need to jump through hoops to simply get the query to run without errors. This wasn't the case with earlier patches of 4.2 SP3.

Unfortunately, we're still experiencing strange behavior: when setting a condition on a universe date object which has no LoV associated to it, the value will reset to the current date upon reopening the query panel.

An example to clarify the issue:

  • create a new Live Office query:

    At the risk of stating the obvious: "Date w/ LoV" has a list of values associated with it, "Date w/o LoV" hasn't. Other than that both universe objects are identical.
    Note the difference in the formatting of the date values.

  • Run the query

  • Reopen the query panel

    The values in the filter on "Date w/o LoV" have been reset to the current date.

  • I've tested this with different universes and saw the same result every time.

An obvious workaround would be to associate a LoV with all date objects, even though this isn't always a good idea.

I'll open a ticket with SAP support to address the issue. Has anyone else encountered this behavior? I couldn't find anything related to this problem. Perhaps Live Office isn't all that popular?

create-query.png (12.6 kB)
reopen-query.png (13.0 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Sep 01, 2017 at 12:57 PM

    I think an SAP support incident is a great idea for this sort of issue. It looks to be product design/functionality that needs to be addressed here.
    Can't comment on popularity, simply do not have numbers.

    Add comment
    10|10000 characters needed characters exceeded

    • Thanks for taking the time to reply Denis.

      There have been new Live Office releases where this specific issue should be fixed, but I haven't gotten around to testing them yet.
      In case anyone comes across this issue: Note 2496033 might help.