Item History no longer working in v15.01.00
See original GitHub issueI’m submitting a …
[x] bug report
…about
[x] edit experience / UI [x] admin experience UI
Current Behavior
When you open an entity/item and click on Item History (previous versions)
you get this error:
[site url] says
Had an error talking to the server (status 400).
Message: Bad Request
Detail: Invalid column name 'CJson'.
Expected Behavior
The list of history items should display.
This site is a clone of a production site still running v14.12.03 where the Item History is still working. It clearly stopped working after the upgrade to 15.01.
Your environment**
- 2sxc version(s): 15.01.00 - - just upgraded from v14.12.03
- Browser: all |
- DNN: v9.10.02
- Hosting platform: IIS, Windows Server 2019 (not-azure)
- Language: any/all
Issue Analytics
- State:
- Created 8 months ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Historical data on WinCC Advanced v15 not working
Hello, I have a problem with the historical data with WinCC Advanced V15 on Windows 7 Professional. I have configured the data logs...
Read more >RSLogix 500
A blank or empty cell indicates that there are no known issues or dependencies.
Read more >MegaRAID Storage Manager v15.03.01.00 for Microsoft ...
Download the latest MegaRAID Storage Manager v15.03.01.00 for Microsoft ... 15.03.01.00 ... CHANGE HISTORY for the MegaRAID Storage Manager.
Read more >MegaRAID Storage Management (MSM) Application v15. ...
Download the latest MegaRAID Storage Management (MSM) Application for Microsoft Windows Server 2003, 2008, and 2012.
Read more >PiCPro V15
DO NOT ATTEMPT to use any G & L Motion Control Inc. product until the use of such product is completely understood. It...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I did the quick fix (SQL) and it worked. Thanks again!!
This looks bad. Basically this implies that some upgrade SQL didn’t run, because we had to rename some columns in the DB which should be installed on v15.00 - of course also on 15.01. I assume you did a direct upgrade from 14.12.x to 15.01.
@tvatavuk could you look into this ASAP?