cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
AdmJLovejoy
Champion Sweeper
Upgraded to 5.2.0.30 and the Assets "Comments" section (under Disk Drives) on the Asset "Summary" page no longer appears in the web console.

Comments are in the tblAssetCustom table, they just disappeared from the Summery page.

Please advise.
Thanks, Jim Lovejoy __________________________________________________________________________________________________ James W. Lovejoy | IBM - Cloud Managed Services Delivery | Infrastructure Architect (Windows Server ...
1 ACCEPTED SOLUTION
Susan_A
Lansweeper Alumni
To help other forum users, could you post what was wrong? Was the field not filled in? The field will only be displayed if it has a value. This has always been the case.

View solution in original post

4 REPLIES 4
Susan_A
Lansweeper Alumni
To help other forum users, could you post what was wrong? Was the field not filled in? The field will only be displayed if it has a value. This has always been the case.
AdmJLovejoy
Champion Sweeper
Disregard, I think I found the issue.
Thanks, Jim Lovejoy __________________________________________________________________________________________________ James W. Lovejoy | IBM - Cloud Managed Services Delivery | Infrastructure Architect (Windows Server ...
AdmJLovejoy
Champion Sweeper
Right, and after the upgrade, it is not there anymore.
Thanks, Jim Lovejoy __________________________________________________________________________________________________ James W. Lovejoy | IBM - Cloud Managed Services Delivery | Infrastructure Architect (Windows Server ...
Susan_A
Lansweeper Alumni
We cannot reproduce this problem. Could you please clarify where the comments disappeared from? Which assets are affected? Where exactly were you seeing the comments?

TblAssetCustom.Comments should be listed in the Summary tab above the asset groups (and still is in our installations). See screenshot attached to this post. Note that the comments found in the Comments tab are stored in tblAssetComments instead.