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 14 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 CultureName or CultureUid. When specifying a PwsCultureRef as an input to a web service, you may specify one or both the CultureName and/or CultureUid. 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 PwsCultureRef is returned in the response to a web service, both the CultureName and CultureUid will be populated, and guaranteed to refer to a single culture.

Format


PwsCultureRef
  • PwsCultureRef
    • CultureId: Int32
    • CultureName: String
    • CultureUid: Int64

Elements


Element

Data Type

Required?

Default

Description

Sample Data

CultureId

Int32

On Insert: No

On Update: No

 

The culture Id is a unique identifier for a culture. For internal use only.

 

CultureName

String

On Insert: Yes

On Update: Yes (if the CultureUid is not supplied)

 

The culture name is a unique identifier for a culture

en-US 

CultureUid

Int64

On Insert: No

On Update: Yes (if the CultureName is not supplied)

 

The culture Uid is a unique and immutable identifier for a culture

1152921504606851419 


Usage Example(s)


Example 01
                    <BillingCultureIdentity>
                        <CultureId i:nil="true"/>
                        <CultureName>en-US</CultureName>
                        <CultureUid>1152921504606851419</CultureUid>
                     </BillingCultureIdentity>
  • No labels