Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The special characters that are not supported in Microsoft FRx


INTRODUCTION

This article describes the special characters that are not supported in Microsoft FRx. Additionally, this article describes why the special characters are not supported and lists the areas in which the special characters are not recommended in Microsoft FRx.

↑ Back to the top


More Information

Special characters that are not supported

A complete list of the special characters that are not supported is as follows:
  • /
  • [
  • ]
  • ;
  • =
  • \
  • :
  • ,
  • .
  • !
  • .
  • -
  • (
  • )
  • *
  • &
  • ^
  • #
  • @
  • $
  • %
  • ?
  • +
  • {
  • }
  • |
  • <
  • >
  • .
  • ~

Why the special characters are not supported in Microsoft FRx

  • Microsoft FRx supports multiple general ledger applications. Therefore, Microsoft FRx can query several different databases. Each database has its own specific requirements. The specific requirements make it difficult to support the special characters. For example, Microsoft Dynamics GP and Microsoft Dynamics SL may handle the special characters differently.

  • Microsoft FRx supports several different output types. Each output type has its own requirements for the special characters. Examples of the output types are as follows:

    • DrillDown Viewer
    • Microsoft Office Excel
    • HTML
    • XML
    • ASCII
    • Printer
  • The Microsoft FRx engine uses a control that performs all the calculations. The Microsoft FRx engine must reserve the following special characters to use in an account description:
    • (
    • )
    • ^
    • *
    • /
    • %
    • \
    • +
    • -
    • >
    • =
    • <
    • &
    • |

    When these special characters exist in other fields, these special characters may interfere with report generation.

Areas in which the special characters are not recommended in Microsoft FRx

  • Building block names or building block descriptions (Row, Column, Tree, or Catalog)
  • Company names or Microsoft FRx company codes (Company Information)
  • Any field in Microsoft FRx that originates from a general ledger

    Note This includes the account description.
  • The Link to GL column in the row layout
  • Any budget ID in the column layout
  • An e-mail address that is entered into the tree or into the catalog layout
  • WebPort folders or report names
  • Windows user names when you use Windows authentication
  • Microsoft Forecaster-specific fields
  • Multidimensional Analysis (MDA) codes
  • Transaction dimension type names in Analytical Accounting for Microsoft FRx

↑ Back to the top


Keywords: kbhowto, kbinfo, kbexpertiseinter, kbexpertisebeginner, kbaxaptafrx, kbgreatplainsfrx, kbmbsmigrate, kbmbspartner, kbnavisionfrx, kbsmallbusinessfinancialsfrx, kbsolomonfrx, kb

↑ Back to the top

Article Info
Article ID : 941691
Revision : 1
Created on : 1/7/2017
Published on : 8/2/2011
Exists online : False
Views : 358