Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Overview


This structure represents the unique key fields associated with identifying a Culture. Cultures govern how numbers are displayed (currency symbol, periods, commas, etc) on invoices. For example, if an engagement's currency is Canadian dollars, you will have two options for culture: English (Canada) and French (Canada). For some currencies, there are no options for Culture. Cultures can be identified by OpsCultureName or OpsCultureNumber. When specifying a PwsOpsCultureRef as an input to a web service, you may specify one or both the OpsCultureName and/or OpsCultureNumber. However, if you do specify both, they must both refer to the same Culture or the Culture reference will not be considered valid. When a PwsOpsCultureRef is returned in the response to a web service, both the OpsCultureName and OpsCultureNumber will be populated, and guaranteed to refer to a single Culture.

Format


PwsOpsCultureRef
  • PwsOpsCultureRef
    • OpsCultureId: Int16
    • OpsCultureName: String
    • OpsCultureNumber: Int16

Elements


Element

Data Type

Required?

Default

Description

Sample Data

OpsCultureId

Int16



The Culture Id, this uniquely identifies a Culture. For internal use only.


OpsCultureName

String



The Culture Name

en-US

OpsCultureNumber

Int16



The Culture Number, this uniquely identifies a Culture

1033

Usage Example(s)


Example 01
                  <EffectiveDefaultOpsCultureIdentity>
                     <OpsCultureId i:nil="true"/>
                     <OpsCultureName>en-US</OpsCultureName>
                     <OpsCultureNumber>1033</OpsCultureNumber>
                  </EffectiveDefaultOpsCultureIdentity>
  • No labels