Service Master View (SVC0200V)

azurecurveProductsFieldService (949)ProjectService Master View (SVC0200V)

Easily find this page again using the shortlink:

Product: FieldService (949)
Series: Project

Display Name: Service Master View
Physical Name: SVC0200V
Technical Name: SVC_Service_MSTR_View

Group Display Name: Service Table Group
Group Technical Name: Service

Seq NoPhysical NameDisplay NameDexterity Data TypeSQL Data TypeLength
1SRVRECTYPE SearchService Record TypeDDL_Service_Record_TypeInteger0
2CALLNBR SearchService Call NumberSTR10_LBAUString10
3ENTDTE SearchEntry DateDT_DateDate6
4COMPDTE SearchComplete DateDT_DateDate6
5SRVSTAT SearchService Call StatusSTR3_LBUString3
6STSDESCR SearchStatus DescriptionSTR30String30
7SRVTYPE SearchService TypeSTR10_LBAUString10
8PORDNMBR SearchPurchase Order NumberPurchase Order NumberString20
9TECHID SearchTech IDSTR10_LBAUString10
10CUSTNMBR SearchCustomer NumberSTR15_RM_Customer_NumberString15
Key to the RM Customer MSTR (RM00101).

Click to show/hide

       ['Service Master View'].CUSTNMBR AS 'Service Master View-Customer Number'
       ,['RM Customer MSTR'].CUSTNMBR AS 'RM Customer MSTR-Customer Number'
       SVC0200V AS ['Service Master View']
       RM00101 AS ['RM Customer MSTR']
                     ['Service Master View'].CUSTNMBR = ['RM Customer MSTR'].CUSTNMBR
11ADRSCODE SearchAddress CodeSTR15_Address_CodeString15
12CUSTNAME SearchCustomer NameSTR64_Customer_NameString64
13Customer_Reference SearchCustomer ReferenceSTR20String20
14CONTNBR SearchContract NumberSTR11String11
15OFFID SearchOffice IDSTR10_LBAUString10
16HISTORY SearchHistoryCB_HistoryBoolean0
17DEX_ROW_ID Searchintint10

DEX_ROW_ID is an auto-numbered IDENTITY column used internally by Dexterity for lock management; it should not be used by developers to identify any particular piece of information.

Microsoft MVP Mariano Gomez has a good write up on the DEX_ROW_ID column.

azurecurveProductsFieldService (949)ProjectService Master View (SVC0200V)

Leave a Reply

Your email address will not be published. Required fields are marked *