Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsReportsReportsReports Module Upgrade Lost Visualizer SettingsReports Module Upgrade Lost Visualizer Settings
Previous
 
Next
New Post
6/9/2007 6:21 PM
 

Upgrading from Reports Module 4.4.2 to 4.5.2, I found that all settings for Settings > Report Settings > Display Settings > Active Visualizer were lost. For my upgrade, Reports Module returned to using the default Active Visualizer > Grid Visualizer, even though I had XSL Transformation Visualizer and a Transform File selected.

I have a portal with a 'growing' number of Reports Module instances using the XSLT Visualizer, and it's not practical to 'reset' settings on all these instances after an upgrade. I'm not sure if this is standard behavior for an Reports Module upgrade. Or maybe it was this one upgrade, from 4.4.2 to 4.5.2, that 'required' losing that setting, and future upgrades will be more sensitive to current settings.

Could anyone else confirm that Reports Module Active Visualizer (HTML or XSL) settings are also lost to Grid Visualizer default when upgrading? Or maybe it was a fluke on my upgrade?


If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
 
New Post
6/10/2007 3:00 AM
 

This is a known issue with the upgrade script and is not actually causing data loss, so you can correct it without reinstalling the module. I will check in to getting a new release (4.5.3) issued with the correct upgrade script, but until then the following solution should work: (Note that while this solution should not cause any data loss, it has not been fully tested so use at your own risk and create a backup if you are worried):

1. Navigate to the Host > SQL page on your portal (after logging in as a SuperUser)

2. Copy, Paste, and Run the followng script, ensuring the "Run as Script" check box is checked

UPDATE {objectQualifier}TabModuleSettings
SET        SettingName = 'dnn_Reports_Visualizer'
WHERE    SettingName = 'dnn_Reports_Renderer'
GO

Our primary goal for upgrades is to preserve all settings, except in extreme circumstances. This issue is an anomaly and should not happen again.

I hope that solves your issue, and thanks for using the module!


Andrew Nurse
DotNetNuke Core Team Member and Reports Module Project Lead
Microsoft Certified Professional Developer

 
New Post
6/10/2007 11:34 AM
 

Thank you for the detailed explanation. And the SQL solution is a good, quick fix. But when I tried the SQL command with 'Run as Script' as you instructed, I get the following:

System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK_TabModuleSettings'. Cannot insert duplicate key in object 'dbo.TabModuleSettings'. The statement has been terminated. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) UPDATE TabModuleSettings SET SettingName = 'dnn_Reports_Visualizer' WHERE SettingName = 'dnn_Reports_Renderer'

I'm not versed enough in SQL to deduce what might be wrong. Any suggestions?


If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
 
New Post
6/10/2007 12:08 PM
 

Ok, this is caused by the fact that because you have used the module a few times since the upgrade, it has created some "dnn_Reports_Visualizer" settings, so it can't rename the settings from the previous version to that name. To fix this, first run this script to rename the incorrectly created settings:

UPDATE {objectQualifier}TabModuleSettings
SET        SettingName = 'old_dnn_Reports_Visualizer'
WHERE    SettingName = '
dnn_Reports_Visualizer'
GO

Then re run this script to convert your previous settings to the new format:

UPDATE {objectQualifier}TabModuleSettings
SET        SettingName = 'dnn_Reports_Visualizer'
WHERE    SettingName = 'dnn_Reports_Renderer'
GO

Finally, assuming everything works correctly, you can then run this script to completely remove the incorrect settings (Don't run this script until you are sure everything is working again):

DELETE FROM {objectQualifier}TabModuleSettings
WHERE SettingName = '
old_dnn_Reports_Visualizer'

My apologies for the complicated workaround, I will work to get this fixed as quickly as possible.


Andrew Nurse
DotNetNuke Core Team Member and Reports Module Project Lead
Microsoft Certified Professional Developer

 
New Post
6/10/2007 3:15 PM
 

Those scripts run in that order worked flawlessly. All my Reports Module instances are working well again. Thank you.

You mention that the Reports Module 4.5.3 rev. and later should not have this 'lost Visualizer setting' upgrade issue, but thank you for providing that detailed workaround now when I really needed it. The scripts saved me much time reconfiguring many Reports Module Visualizer settings lost since the 4.5.2 upgrade.


If a problem can be solved, there's no use worrying about it.
If it can't be solved, worrying will do no good.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsReportsReportsReports Module Upgrade Lost Visualizer SettingsReports Module Upgrade Lost Visualizer Settings


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out