Skip to main content
Russell Campbell
Known Participant
Oct 2, 2025 2:08 PM UTC

Gotcha items for Cityworks update from 15.8.8 to 23.11?

Our next step on the eventual path to Unity Maintain per documentation seems to be to get our on premises install up to the latest 23.x version, currently 23.11. I’ve been doing some reading and research and found this article very helpful: https://cityworks.my.site.com/s/article/UpgradeFrom15-8-xTo23-x.

 

The article is dated 1/29/2025 so it came out prior to 23.11. If I understand correctly we can jump straight to the latest 23.x by doing the following:

  1. Run the 23.2 Database Manager and Data Migration tools
  2. Run the 23.11 overall application installs (we intend to go with Office Companion in parallel) including Database Manager and Data Migration again.

 

The intent is to install the 23.11 Office Companion on the existing site url and the 23.11 Cityworks application on its own new url on the same server.

 

Immediate question(s) are:

  • While an oversimplification, is that really it?
  • Do we need to also run the Database Manager and Data Migration tools at any other patch level between 23.2 and 23.11 before running the 23.11 install?
  • There are some other items I'm aware of like the change to Active Reports and migrating our custom reports and integrations but...does anyone have any other significant possible "gotcha" items to watch out for and prep in advance of installs?

 

 

    5 replies

    Alan Marsh
    Participating Frequently
    Oct 2, 2025 4:12 PM UTC

    The article is accurate I've done this on all of our servers. We have an issue with 23.11 that prevents us from using docx templates to print/email the work orders (DEV-16567)

    Also, in storeroom you can't print the transaction query due to the Active report issue. We are currently on 23.10 but that has been sunseting. So, at this point I am just waiting for 23.12 and hope some of the issues are fixed.

    Translate
    Russell CampbellAuthor
    Known Participant
    Oct 2, 2025 4:12 PM UTC

    Super. Thanks for the response.

    Translate
    Jacob Pitsch
    New Participant
    Oct 2, 2025 4:13 PM UTC

    This may or may not be helpful to you, but I encountered a lot of errors surrounding browser caching when I was doing my testing. It is truly maddening that everything is now done from the host installer on localhost, because browsers are susceptible to caching. There could be nothing wrong at all, and you might just spin your wheels. Make sure to keep clearing cache or trying different browser if you encounter unexpected behaviors.

    Translate
    Allen White
    New Participant
    Oct 2, 2025 4:13 PM UTC

    Are you using any custom tools that call on the Cityworks APIs from within HTML widgets on dashboards or by injection to the XML pages?

    Translate
    Chris Saxon
    New Participant
    Oct 2, 2025 4:13 PM UTC

    Highly recommend very thorough testing. They expect you to use Respond and may have removed Office functionality. Things that worked in Office may not work because of new security settings for Respond. One specific example is if you have PLL and Public Access. They removed the functionality to approve user logins if the automatic registration doesn't work for some reason. You have to manually delete records in the database to clear them out (bad practice).

    Translate
    Terms & ConditionsAccessibility statement