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 Caches explained

Microstrategy Caches Improving Response Time: Caching A  cache is a result set that is stored on a system to improve response time in future requests.  With caching, users can retrieve results from Intelligence Server rather than re-executing queries against a database. To delete all object caches for a project 1 In Developer, log into a project. You must log in with a user account that has administrative privileges. 2 From the  Administration  menu, point to  Projects , and then select  Project Configuration . The Project Configuration Editor opens. 3 Expand  Caching , expand  Auxiliary Caches , then select  Objects . To delete all configuration object caches for a server 1 Log in to the project source. 2 From the  Administration  menu in Developer, point to  Server , and then select  Purge Server Object Caches . 4 Click  Purge Now . To purge web cache follow the steps in the link ...

Predictive modelling in Data Science using Microstrategy

Creating a predictive modelling in MicroStrategy MicroStrategy Data Mining Services has been evolving to include more data mining algorithms and functionality. One key feature is MicroStrategy Developer’s Training Metric Wizard. The Training Metric Wizard can be used to create several different types of predictive models including linear and exponential regression, logistic regression, decision tree, cluster, time series, and association rules. Linear and exponential regression The linear regression data mining technique should be familiar to you if you have ever tried to extrapolate or interpolate data, tried to find the line that best fits a series of data points, or used Microsoft Excel’s LINEST or LOGEST functions. Regression analyzes the relationship between several predictive inputs, or independent variables, and a dependent variable that is to be predicted. Regression finds the line that best fits the data, with a minimum of error. For example, you have a dataset ...

Custom Tooltips in Microstrategy developer and Web

Custom Tooltips in Microstrategy developer and Web The following table describes the macros you can use to customize graph tooltips in both MicroStrategy Developer and MicroStrategy Web: Macro Information Displayed {&TOOLTIP} All relevant labels and values associated with a graph item. {&GROUPLABEL} Name of the graph item's category. This value is often the graph item's attribute element information, as attributes are commonly used as the categories of graph reports. {&SERIESLABEL} Name of the graph item’s series. This value is often the graph item's metric name information, as metrics are commonly used as the series of graph reports. {&VALUE} The value of a given data point. {&XVALUE} The X-value of a data point. Only applicable to Bubble charts and Scatter plots. {&YVALUE} The Y-value of a data point. Only applicable to Bubble charts and Scatter plots. {&ZVALUE} The Z-value of a data point. Only applicable to Bubble charts and Scatter plots. {...

Logical Views to specify an outer join between two attribute lookup tables when only attributes are on a report

Logical Views to specify an outer join between two attribute lookup tables when only attributes are on a report Apart from using the VLDB properties to create the left outer join,  article describes how to use the Logical View to specify an outer join between two attribute lookup tables when only attributes are on a report. This method exists as attribute only outer joins will not be generated on their own by the MicroStrategy SQL engine. This is because they are only necessary with r agged/unbalanced hierarchies which are not supported as null attribute IDs are not supported (parent elements with no child elements or child elements with no parents).  Brief instructions are provided using the example below. Consider, two attributes: Parent01 and Child01 have a parent-child relationship. Their Lookup tables are defined, as follows Parent01 Child01 Note that although there are 4 ID values for the attribute Parent01, there is no defined relationship ...

Fiscal Week, Fiscal Month, Fiscal Quarter and Fiscal Year calculations in Microstrategy

Fiscal Week, Fiscal Month, Fiscal Quarter and Fiscal Year calculations in Microstrategy FiscalWeek Returns the numeric position of a week within a fiscal year, for a given  input date. This function is useful in financial reporting when the start of the fiscal year is different than the start of the calendar year. Syntax FiscalWeek< firstWeekDay ,  firstMonth >( Date / Time ) Where: • Date / Time  is the input date or timestamp. • firstWeekDay  (default value is 1) is a parameter that determines which day of the week is considered as the first day of the week. You can type an integer value from 1 to 7, with 1 representing Sunday, 2 representing Monday, and so on until 7 representing Saturday. • firstMonth  (default value is 1) is a parameter that determines which month is considered as the start of the fiscal year. You can type an integer value from 1 to 12, with 1 representing January, 2 representing February, and so on until ...

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

Replace object names in bulk using MicroStrategy Repository Translation Wizard

Replace object names in bulk using MicroStrategy Repository Translation Wizard Users may need to replace  object names  in bulk.  This can be done using MicroStrategy Repository Translation Wizard in MicroStrategy Developer 9.4.x - 10.x.  Follow the steps below for an example of how to do this.  Create an empty MD shell in Microsoft Access.  Run Repository Translation Wizard from the Start Menu -> Programs -> MicroStrategy-> Object Manager In the "Metadata Repository" screen, select the "Project Source Name" and check the "Export Translations" option, as shown in the following screen shot: In the "Languages" screen, select a project, a translation reference language and a language (choose English as default), as shown in the following screen shot: In the "Select objects" screen, if one needs to select a certain type of object, check the option  Use the results of a search object .  Then, click 'New' to...

Create a transaction services photo uploader

Create a transaction services photo uploader   1.  Create a new table "photo_upload" in Tutorial warehouse database (the default location: C:\Program Files\MicroStrategy\Tutorial Reporting\TUTORIAL_DATA_7200.mdb), as shown below:    2. The 'photo_upload' table has to be pre-populated with *exactly* 10 rows of data, the values for the 'ID' column should be 1-10 and the values for the 'uploaded' column should all be 0 3.  In MicroStrategy Desktop, create a freeform report "R1" based on the new table "photo_upload" in Tutorial data created at step 1, as shown below:   SELECT Location, Description, ID, uploaded, numbers FROM PHOTO_UPLOAD 4.  Create another table for transaction insert SQL. Make sure to create an 'autonumber' type ID as primary key for this table, or auto_increment ID for different DBs.                     5. Create...

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

Super Cubes in MicroStrategy 2019

Super Cubes in MicroStrategy 2019 Beginning in MicroStrategy 11.0 and 2019, users will notice objects referred to as " Super Cubes ".  Super Cubes are simply a renaming of what was previously referred to as MTDI (Multi Table Data Import) Cubes. Note that only the naming convention has changed, as the functionality remains the same . This name change is visible in MicroStrategy Workstation and MicroStrategy Web. In MicroStrategy Workstation, right click on any cube created via Data Import and select Properties . The object Type is listed as Super Cube: This can also be seen when editing or authoring a dossier. In your Datasets panel, hover over the name of your dataset. The tooltip will show the dataset type listed as a Super Cube.