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

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:...

Microstrategy Document Autotext macros:

Autotext  code/macros in  Microstrategy Document/dashboard This is a list of the available auto text macros that the Report Services Document engine recognizes. The following auto text codes allow you to add  document variable information to your document. These auto text codes are automatically replaced by information about the document. Auto text codes for MSTR document/dashboard:  AUTOTEXT DESCRIPTION   {&PAGE}  Display the current page.  {&NPAGES}  Display the total number of pages.  {&DATETIME}  Display the current date and time.  {&USER}  Display the user name that is executing the Report Services Document.  {&DOCUMENT}  Display the document name.  {&DOCUMENTID}  Display the document ID.  {&DESCRIPTION}  Display the document description.  {&PROJECT}  Display the project name.  {&EXECUTIONTIME}  Dis...

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...

Types of prompts in Microstrategy

Types of prompts in Microstrategy The different types of prompts allow you to create a  prompt  for nearly every part of a report. Prompts can be used in many objects including reports, filters, metrics, and custom groups, but all prompts require user interaction when the report is executed. The correct prompt type to create depends on what report objects you want users to be able to base a filter on to filter data, as described in the list below. Filter definition prompts   allow users to determine how the report's data is filtered, based on one of the following objects: Attributes in a hierarchy : Users can select prompt answers from one or more attribute elements from one or more attributes. The attribute elements that they select are used to filter data displayed on the report. This prompt lets you give users the largest number of attribute elements to choose from when they answer the prompt to define their filtering criteria. For example, on a repor...

Error. Engine Attribute Role Limit Exceeded! To get rid off this error: (1) Turn off Engine Attribute Role setting in VLDB dialog

Error. Engine Attribute Role Limit Exceeded! Some times Microstrategy will give the below error when updating the schema after an attribute is created. MicroStrategy Developer --------------------------- Error(s) occurred while loading schema: [DFCSCHEMA] Population Exception: The object shown in the following hierarchy no longer exists in schema: -Table LKUP_TEST_FEE_SHIPMENTS error. Engine Attribute Role Limit Exceeded! To get rid off this error: (1) Turn off Engine Attribute Role setting in VLDB dialog; OR (2) Use Table Alias featureDSSSQLEngine: Schema loading error: Message from GetErrorInfo : Report cache is not found.. Error(s) occurred while loading schema: 63. CAUSE: This error message means that the table shown in the error text needs to be split into a very large number tables. MicroStrategy has a limitation that only allows one table to be split into no more than 100 tables. The error above is shown when this limitation is surpassed....

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...

Personalizing file locations, email and file subscriptions using macros in Microstrategy

Personalizing file locations MSTr allows to dynamically specify the  File Location  and  Backup File Location  in a file device using macros.  For example, if you specify the  File Location  as  C:\Reports\{&RecipientName}\ ,  all subscriptions using that file device are delivered to subfolders of  C:\Reports\ . Subscribed reports or documents for each recipient are delivered to a subfolder with that recipient’s name, such as  C:\Reports\Jane Smith\  or  C:\Reports\Hiro Protagonist\ . The table below lists the macros that can be used in the  File Location  and  Backup File Location  fields in a file device: Description Macro Date on which the subscription is sent {&Date} Time at which the subscription is sent {&Time} Name of the recipient {&RecipientName} User ID (32-character GUID) of the recipient {&RecipientID} Distribution Services add...

Microstrategy Dossiers explained

Microstrategy  Dossiers With the release of MicroStrategy 10.9, we’ve taken a leap forward in our dashboarding capabilities by simplifying the user experience, adding storytelling, and collaboration.MSTR has  evolved dashboards to the point that they are more than dashboards - they are  interactive, collaborative analytic stories . Ultimately, it was time to go beyond dashboards, both in concept and in name, and so  the've  renamed VI dashboards to  ‘ dossiers ’.  Dossiers can be created by using the new Desktop product or Workstation or simply from the Web interface which replaces Visual Insights. All the existing visual Insights dashboards will be converted to Dossiers   With MicroStrategy 10.9, there was an active focus on making it easier to build dashboards for the widest audience of end users. To achieve this, some key new capabilities were added that make it easier to author, read, interact and collaborate on dashboards ...
Microstrategy Release Types Platform release Interval:  Annually every twelve (12) months in December Who:  Entire customer base What:  Focus on production level security, stability, and performance defect fixes for all customers. Expectation:  Customer has chosen platform path and wants product stability without new enhancements. Support:  Three (3) years, patches for approved P1 defects, and regular hotfix cadence addresses critical defects. Feature Release Interval:  Quarterly every three (3) months Who:  Customers with specific feature requirements. What:  New functionality developed in close collaboration with customers and customer council. Expectation:  Customer has chosen feature path, will consume further feature releases. Support:  Six (6) months patch support for approved P1 defects and (eighteen) 18 months troubleshooting. Customers upgrade to next feature release for roll-up f...