Columns not matching because field is not saved in DB (as expected) - Data Springs Inc. - DotNetNuke Modules - DotNetNuke Module Product Forums - Product Discussion - DotNetNuke Modules

Columns not matching because field is not saved in DB (as expected)

Last Post 05-23-2013 01:54 PM by Alain Darwich. 2 Replies.

Author

Messages

Alain Darwich User is Offline

new to the springs
Posts:2
Avatar

05-16-2013 11:35 AM
Hi there, Thanks in advance for your help with this. We have 2 email fields, one for email and the other for email verify. The email verify is being added into the XLS export (the results) in the header, but the content for it is not exporting, which I assume is because it is not saved in the DB. Since this field is not saved in the DB, the header should not be there, right? Because the header is there and the content is not, the columns are all one off beginning with the email column. For example: First Name,Last Name,Email,Email Verify,City,State John,Smith,john@domain.com,New York,NY rather than First Name,Last Name,Email,City,State John,Smith,john@domain.com,New York,NY Thanks!

Chad Nash

Posts:5260

05-23-2013 10:31 AM
Hi Alain, Thank you for your feedback. Just a couple of comments here: In newer versions of the module you get to determine which fields are allowed to be exported, so make sure you are on the very latest 4.1 release when we added those features. We also have a sister product called Dynamic Views and this product allows you to sync to Dynamic Forms for very custom / searchable reports and exports to PDF and excel. This feature also allows you to choose which columns can be exported to Excel as well. Let me know of you have any other questions! Thanks, Chad

Alain Darwich User is Offline

new to the springs
Posts:2
Avatar

05-23-2013 01:54 PM
Hi Chad, Thanks for the reply! We can upgrade to 4.1 I suppose but the issue seems to be not that I can't choose which fields to export or not-export but because the item is selected to not save in the database, it is not exporting properly. The header in the XLS exports but not the data. Does that make sense? So it seems like a bug where the header is there but it shouldn't be? If the only solution is an upgrade I can advise them that is what they need to do. Thanks for your help! Alain