Skip to main content

Microstrategy Custom number formatting symbols

Custom number formatting symbols

If none of the built-in number formats meet your needs, you can create your own custom format in the Number tab of the Format Cells dialog box. Select Custom as the Category and create the format using the number format symbols listed in the table below. Each custom format can have up to four optional sections, one each for:
  • Positive numbers
  • Negative numbers
  • Zeros
  • Text
Each section is optional. Separate the sections by semicolons, as shown in the example below:
#,###;(#,###);0;"Error: Entry must be numeric"
For more examples, see Custom number formatting examples.
To jump to a section of the formatting symbol table, click one of the following:

Numeric symbols

For details on how numeric symbols apply to the Big Decimal data type, refer to the Project Design Guide.
Symbol
General
General
Displays the number in General format, that is, no specific number format.
0
Digit placeholder.
  • If the number contains fewer digits than the format contains placeholders, the number is padded with zeros. For example, the format code 00000 displays the number 12 as 00012.
  • Use this placeholder for mandatory zeros.
  • If there are more digits to the right of the decimal point than placeholders in the format, the decimal portion is rounded to the number of places specified by the placeholders.
  • If there are more digits to the left of the decimal point than the placeholders in the format, the extra digits are retained.
  • If the format contains zeros to the left of the decimal point, numbers less than one are displayed with a zero to the left of the decimal point.
#
Digit placeholder.
  • This digit placeholder displays only significant digits and does not display insignificant zeros. For example, the format code ##.## displays the number 0025.360 as 25.63.
  • Use this placeholder to indicate optional zeros.
  • If there are more digits to the right of the decimal point than placeholders in the format, the decimal portion is rounded to the number of places specified by the placeholders.
  • If there are more digits to the left of the decimal point than the placeholders in the format, the extra digits are retained.
  • If the format contains only number signs (#) to the left of the decimal point, numbers less than one are displayed beginning with a decimal point. For example, the format #.00 will display the number 0.43 as .43.
?
Digit placeholder.
  • This digit placeholder adds spaces for insignificant zeros on either side of the decimal point so that decimal points align when formatted with a fixed-width font.
  •  You can also use question marks (?) for fractions that have varying numbers of digits.
%
Displays the number as a percentage, by multiplying the number by 100 and appending the percent character (%).
,
(comma)
Thousands separator.
  • If the format contains commas separated by number signs (#) or zeros, a thousands separator is used in the formatted text.
    The actual thousands separator used depends on the session locale.
  • A comma following a placeholder scales the number by a thousand. For example, using 0, scales the number by 1000, so that 10,000 displays as 10.
.
(period)
Decimal separator.
The actual decimal separator used depends on the session locale.

E-
Scientific notation.
  • If the format contains a scientific notation symbol to the left of a 0 or # placeholder, the number is displayed in scientific notation and an E or
  • The number of 0 and # placeholders to the right of the decimal determines the number of digits in the exponent.
  • E- and e- place a minus sign by negative exponents.
  • E+ and e+ place a minus sign by negative exponents and a plus sign by positive exponents.
       Return to list

Character/text symbols

Symbol
Description
"text"
Displays the text inside the quotation marks. Even if the text is a valid formatting symbol, it is treated as literal text if it appears within quotes.
Use quotation marks around any character that is not a formatting symbol, including a space, the dollar sign ($), minus sign (-), slash (/), exclamation mark (!), ampersand (&), tilde (~), curly brackets ({ }), equals sign (=), less than and greater than signs (< >), and the caret (^). This ensures that the text appears correctly in both MicroStrategy Developer and MicroStrategy Web.
:
In a date/time format, the colon (:) does not need to be enclosed in double quotation marks (" "). However, to display it in a numeric format, it must be enclosed in quotes. For example, if you have an integer that must be displayed as 12:34:56, the correct format is "##":"##":"##".
*
The asterisk (*) repeats the next character until the width of the column is filled. Only one asterisk can be used in each format section.
_
The underline ( _ ) skips the width of the next character. For example, to make negative numbers surrounded by parentheses align with positive numbers, you can include the format _). Positive numbers will then skip the width of a parenthesis.
       Return to list

Date and time symbols

Symbol
Description
m
Month number.
Displays the month as digits without leading zeros, such as 1.
Can also represent minutes when used with the h or hh formats.
mm
Month number.
Displays the month as digits with leading zeros, as in 01.
Can also represent minutes when used with the h or hh formats.
mmm
Month abbreviation, such as Jan.
mmmm
Month name, such as January.
d
Day number.
Displays the day as digits with no leading zeros, such as 1.
dd
Day number.
Displays the day as digits with leading zeros, as in 01.
ddd
Day abbreviation, such as Sun.
dddd
Day name, such as Sunday.
yy
Year number.
Displays the year as a two-digit number, such as 03.
yyyy
Year number.
Displays the year as a four-digit number, such as 2003.
h
Hour number.
Displays the hour as a number without leading zeros, such as 1.
If the format contains an AM or PM format, the hour is based on a 12-hour clock; otherwise, it is based on a 24-hour clock.
hh
Hour number.
Displays the hour as a number with leading zeros, as in 01.
If the format contains an AM or PM format, the hour is based on a 12-hour clock; otherwise, it is based on a 24-hour clock.
m
Minute number.
Displays the minute as a number without leading zeros, such as 1.
The m format must appear immediately after the h or
mm
Minute number.
Displays the minute as a number with leading zeros, such as 01.
The mm format must appear immediately after the h or hh symbol; otherwise, it is interpreted as month.
s
Second number.
Displays the second as a number without leading zeros, such as 1.
ss
Second number.
Displays the second as a number with leading zeros, such as 01.
AM/PM
am/pmA/P a/p
12-hour time.
Displays time using a 12-hour clock. Displays AM, am, A, or a for times between midnight and noon; displays PM, pm, P, or p for times from noon until midnight.
[h]
Total number of hours.
[m]
Total number of minutes.
[s]
Total number of seconds.
       Return to list

Currency symbols

You can include the following currency symbols in a number format. Keep the ALT key pressed and type the ANSI code of the currency. The ANSI code should be followed by the format code for the number.
To type ANSI code for the currency symbol, turn on NUM LOCK and use the numeric keypad. As you type the ANSI code, the Custom box appears blank. The currency symbol is displayed only when you finish typing the code.
Press the ALT key and type this code:
To Display:
0162
¢
0163
£
0165
¥
0128

Text color symbols

Symbol
Description
[Black]
Displays cell text in black.
[Blue]
Displays cell text in blue.
[Cyan]
Displays cell text in cyan.
[Green]
Displays cell text in green.
[Magenta]
Displays cell text in magenta.
[Red]
Displays cell text in red.
[White]
Displays cell text in white.
[Yellow]
Displays cell text in yellow.
       Return to list

Conditional symbols

Symbol
Description
[conditional value]
Designates a different condition for each section.
For example, data in a column has values ranging from 200 to 800. You want the text "Poor" to display in black for values less than 400, "Good" to display in red for values greater than 600, and "Average" for values between 400 and 600. You can use the following code:
[<400][Black]"Poor";[>600][Red]"Good";[Blue]"Average"
In this example, [<400] and [>600] are the conditional values.

Comments

Post a Comment

Popular posts from this blog

Apply or Pass-through functions in Microstrategy

Ap ply (Pass-Through) functions MSTR Apply functions provide access to functions or syntactic constructs that are not standard in MicroStrategy but are provided by various RDBMS systems.. Syntax common to Apply functions Apply Function Name   ("expression with placeholders", Arg1, Arg2, Arg3, …ArgN) where: Apply Function Name  – is a generic name used for the predefined pass-through functions described above expression with placeholders  – is the string describing the actual expression or syntax that the engine uses while generating the SQL and which is sent to the RDBMS. The placeholders are represented by #0, #1, and so on. "#" is a reserved character for MicroStrategy. Arg  – is an argument that replaces the parameter markers in the pattern. Arg1 replaces #0, Arg2 replaces #1, and so on. There are   five  pre-defined Apply functions to replace regular, predefined functions of the same type. For more details, cli...

Case functions Microstrategy

Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. In general, a user specifies a list of conditions and corresponding return values. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. If all conditions are false, a default value is returned.  Case  can be used for categorizing data based on multiple conditions. This is a single-value function. Syntax Case ( Condition1 ,  ReturnValue1 ,  Condition2 , ReturnValue2 ,...,  DefaultValue ) Example Case(([Total Revenue] < 300000), 0, ([Total Revenue] < 600000), 1, 2) sum(Case (Day@DESC in (“Sat”,”Sun”), Sales, 0) {~+} Sum(Case(Category@DESC In("Books","Electronics"),Revenue,0)){~+} CaseV (case vector) CaseV  evaluates a single metric and returns different values according to the results. It can be used to perfo...

Microstrategy "Error type: Odbc error. Odbc operation attempted

 "Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [HYT00:0: on SQLHANDLE] [MicroStrategy][ODBC Oracle Wire Protocol driver]Timeout expired" is shown when executing reports from Web When users are trying to execute some reports in MicroStrategy web in particular, they may receive the Error “SQL Generation Complete Index out of range” and “Timeout expired” error as shown below: Possible Causes: One possible cause is that the MicroStrategy Intelligence Server using a cached database connection that was already dropped by the RDBMS. To resolve this: Admin should delete the database connection caches and create a new DSNs in case they are sharing DSNs to connect to different databases. In addition, change the settings for the ‘Connection lifetime’ and the ‘Connection idle time out’.  Follow the steps below to perform the mentioned changes and verify the report after each step and some of the settings require i-server r...

MicroStrategy URL API Parameters

MicroStrategy URL Structure The following table summarizes the root URL structure used for every request to MicroStrategy Web. Environment Main Application URL Administration URL J2EE http://webserver/MicroStrategy/servlet/mstrWeb http://webserver/MicroStrategy/servlet/mstrWebAdmin .NET http://webserver/MicroStrategy/asp/Main.aspx http://webserver/MicroStrategy/asp/Admin.aspx Every request sent to MicroStrategy Web calls a central controller. Parameters are appended to  Main.aspx  or  mstrWeb  (in a .NET and J2EE environment, respectively) to indicate to the controller how the request should be internally forwarded and handled. The following examples show a URL for accessing a MicroStrategy folder when the user does not have an existing session. The URL contains not only the parameters needed to connect to MicroStrategy Web, but also the parameters needed to log on and create a session. J2EE environment: <a href="http:...

Derived metric based on attribute values

Derived metric based on attribute values Here is how could create and display data correctly on using below simple steps.  Create a report with Category, Subcategory and Revenue. Create New Metric in a report or VI.  Case((Category@ID = 1), Revenue, 0) Booksand Name it as Revenue for  where 2 is Category ID for "Books"  Report will display result as below.  Result for new metric is blank. Now to fix this create a new Derived metric on Category attribute first with formula as  Max(Category) {~ }  and calling Books Now Edit the "Revenue for Books metric and Replace Category@ID with this new Books metric formula would looks like this  Case((Books = 1), Revenue, 0).  Report result would now display as expected as shown below

Control the display of null and zero metric values

Show   Control the display of null and zero metric values in a grid report You can determine how to display or hide rows and columns in a grid report that consist only of null or zero metric values. You can have MicroStrategy hide the rows and columns in the following ways: Hide rows and columns that consist only of null metric values Hide rows and columns that consist only of zero metric values Hide rows and columns that consist only of null or zero metric values (default) Once you have defined how MicroStrategy hides null and zero metric values in the grid, you can quickly show or hide the grid using the Hide Nulls/Zeros option in the Data menu, as described below, or by clicking the  Hide Nulls/Zeros  icon  in the Data toolbar. To determine how null and zero metric values are displayed or hidden in a grid report Open the report in Edit mode. From the  Tools  menu, select  Report Options . The Report Options...

Bursting file subscriptions Microstartegy

Bursting file subscriptions: Delivering  parts of reports across multiple files: Large MicroStrategy reports and documents are often broken up into separate pages by attributes. In a similar way, with Distribution Services, you can split up, or burst, a report or document into multiple files. When the subscription is executed, a separate file is created for each element of each attribute selected for bursting. Each file has a portion of data according to the attributes used to group data in the report (page-by axis) or document (group-by axis). Ex:, you may have a report with information for all regions. You could place Region in the page-by axis and burst the file subscription into the separate regions. This creates one report file for each region. As a second ex:, if you choose to burst your report using the Region and Category attributes, a separate file is created for each combination of Region and Category, such as Central and Books as a report, Central and Ele...

Transaction Services - Configure Transactions

Configure Transactions in MSTR Web Transaction Services-enabled document displayed on an iPhone, iPad, or Android device can allow users to insert/update/delete data in to the database, using the options in the Configure Transactions Editor. To do so, you must link a Transaction Services report to a grid or to text fields in a panel stack. If the document is being displayed on an iOS device, you can link the report to the cells of a transaction table. Data from the input objects defined in the Transaction Services report is displayed in the grid, text fields, or cells for users to edit. Prerequisites:        Ø   You must have the Web Configure Transaction privilege assigned by MSTR user admin. Ø   Create the Transaction Services report (usually a grid report) you want to link to the grid, text fields, or transaction table cells. Make sure that the Transaction Services report must contain the input object for each value you w...

Settings for Outer Join between metrics in MicroStrategy

Settings for Outer Join between metrics in MicroStrategy MicroStrategy adopts multi-pass logic to determine the execution plan for a report. This means that every metric is evaluated in separate SQL passes. Outer Joins come into play when MicroStrategy Engine merges the results from all SQL passes into one report. For a multi-pass report, different Outer Join behaviors can give the user completely different results. In addition, report metrics can be of different types which can, in some cases, influence the result of the outer join. In MicroStrategy, there are two settings that users can access to control Outer Join behavior : Formula Join Type and Metric Join Type . Metric Join Type: VLDB Setting at Database Instance Level Report and Template Levels Report Editor > Data > Report Data Options Metric Level   Metric editor > Tools > Metric Join Type Control Join between Metrics Formula Join Type: Only at Compound/Split...