1. 

   nsepetys, Member

   Hi myDBR Representative,

   How are you? We recently updated to version 4.6.1 (build 2960) and I am noticing the string column styling is no longer being respected for Excel exports (could be other export types too- I haven't confirmed). We need the string styling for values that can be interpreted as integers but should override any local preferences that determine normal integer formatting behavior (with or without commas as delimiters of the text). The scenario is like below:

   SELECT 'dbr.colstyle', 'ourcolumn', '%s'; SELECT 32432 AS 'The Value[ourcolumn]';

   Expected output is the cell value = "32432"

   The current output in HTML is correct. Excel, however, shows "32,432".

   The short term work-around seems to be to return the column values casted as CHARs but I'd like to know if there's a way to get this addressed without refactoring the reports that use the above method for column styling. Your help is appreciated.

   Thanks!
   Noah
2. 

   myDBR Team, Key Master

   The supported format for not using the formatting is '%d'. Do not cast numbers to strings as they are then treated as strings.

   --
   myDBR Team
3. 

   nsepetys, Member

   Interesting. Good to know. Thanks for the info!
4. 

   myDBR Team, Key Master

   We added support for '%s' as well. Works with floats too.

   --
   myDBR Team
5. 

   nsepetys, Member

   Thanks! That'll save me from refactoring all our reports.
6. 

   myDBR Team, Key Master

   Just run the updater.

   --
   myDBR Team

Reply

You must log in to post.