Private Text Showing on reports

On internal and client facing reports(both custom and canned), private text is showing despite the "hide private text" box being checked.  This worked in TS 2011 but ever since conversion to TS 2017, it does not work as designed.

  • 0
    Take a backup of the database before you do any of this.

    Go to Setup > General > Other > Change your private text indicator to anything else and click OK.
    Close Timeslips > reopen it > Go back to General settings and change the private text indicator back to what it was originally and click OK.
    Now try your reports again.
  • 0 in reply to Claire98
    Thanks, the reports are still broken though. Timeslips has confirmed that this is a broken feature and has kicked it back to development. This is the second broken feature, that I know of, that they have kicked back to development for TS 2017.
  • 0 in reply to adonders
    adonders:

    I don't really have a solution to your issues, but I did just want to take a moment and acknowledge how frustrating the upgrade seems to have been for you. From the issues you are posting, you seem to be a deep user of Timeslips and it is always disheartening when a long time deep user has trouble with an upgrade. Seems software is never perfect, but it is particularly frustrating when something that you used to depend on that worked, gets broken on an upgrade.

    I have done several upgrades to v2017 now, and while I have had an occasional issue (most recently the slow reprint pull up), none of my clients has had the perfect storm of multiple issues that seem to have befallen you.

    Hoping that development can get them worked out for you soon. And keep posting!!! It both lets us know where the problems are, adding to the collective "brain trust," and may eventually possibly get you some solutions.
  • 0 in reply to Nancy Duhon
    Does anyone know if trouble ticket 8005886809, which relates to this broken feature, is being included in the April service release?
  • 0 in reply to adonders
    The printing of private text was not corrected, no. After investigation, I found that the original issue started at the release of Timeslips 2012, and was first reported - by you, thank you! - to Timeslips on January 30, 2017.

    It may be a very simple fix and be corrected in the next service release, but I wanted to be sure to give you a frame of reference.
  • 0 in reply to RogerS
    Thank you, Based on a reliable source, this will not be fixed in Timeslips 2017 as the April release will likely be the last. It is baffling that despite the fact that Timeslips had a ticket, they failed to fix the issue they broke. We had to roll back to TS 2011 because of this issue. Hopefully they will fix it in 2018 but I cannot justify purchasing it since we already paid for 2017 which we could not use.
  • 0 in reply to adonders
    I am sorry to hear you say that, Mr. Donders. I do see from your account that indeed, you last purchased Timeslips back in 2011 and so as a casual user of the program, have missed out on many updates over the years, and certainly will be missing out on the reliability of the SQL database used in 2017 at a minimum.

    Business Care support plan holders will automatically get the 2018 version of Timeslips and will get the updates/enhancements associated with it.

    Again, this issue has existed for many years, and apparently has had a very minimal impact on more recent Timeslips users. We don't usually see internal reports presented to clients, and as such the issue wouldn't normally be a 'show stopper'.

    I could see an easy workaround using Notes on a slip instead of Private Text as an immediate fix and still be able to use the 2017 version and all of it's benefits
  • 0 in reply to RogerS
    We actually purchased TS 2017 and did not expect Timeslips to break something. Coupled with the fact that they issued ticket # 8005886809 which should have been fixed in the April release. What is the purpose of a ticket and a promise if it gets ignored?
  • 0 in reply to adonders
    We also rely heavily on TSimport so there is no corresponding field for notes.