Adding a Connection to Microsoft Dynamics GP

To add a connection to Microsoft Dynamics GP:

1. In the application console, navigate to the Connections page.
2. At the Add Connections panel, select the icon for the connection you want to add.
3. If the Microsoft Dynamics GP icon is not available, click the Add More icon to download and install the Microsoft Dynamics GP connector from the CData site.

For required properties, see the Settings tab.

For connection properties that are not typically required, see the Advanced tab.

Connecting to Microsoft Dynamics GP

To connect set URL to the Web services endpoint; for example, http://{servername}:{port}/Dynamics/GPService. Additionally, set CompanyId to the unique identifier of the company you are connecting to. You can obtain this value by querying the Company table and leaving the property empty.

Authenticating to Microsoft Dynamics GP

The Microsoft Dynamics GP data source supports the following authentication methods:

• Anonymous Authentication
• WS-Security (WSS) Authentication
• Basic Authentication
• NTLM User Authentication
• Digest
• Negotiate (Kerberos)

Anonymous Authentication

In some situations, you can connect to Microsoft Dynamics GP without setting any authentication connection properties. To do so, set the AuthScheme to None, and you are ready to connect.

WS-Security (WSS)

Set the User and Password to connect and set AuthScheme to WSS.

Note: WSS Authentication is the default authentication scheme.

Basic

Set the User and Password to connect and set AuthScheme to Basic.

Windows (NTLM)

Set the Windows User and Password to connect and set AuthScheme to NTLM.

Digest

Set the User and Password to connect and set AuthScheme to Digest.

Kerberos

See Using Kerberos for details on how to authenticate with Kerberos.

Fine Tuning Data Access

The Sync App returns data summaries by default to save performance. Set LookupIds to true to return details such as line items; however, note that entities must be retrieved one at a time.

Kerberos

To authenticate to Microsoft Dynamics GP with Kerberos, set AuthScheme to NEGOTIATE.

Authenticating to Microsoft Dynamics GP via Kerberos requires you to define authentication properties and to choose how Kerberos should retrieve authentication tickets.

Retrieve Kerberos Tickets

Kerberos tickets are used to authenticate the requester's identity. The use of tickets instead of formal logins/passwords eliminates the need to store passwords locally or send them over a network. Users are reauthenticated (tickets are refreshed) whenever they log in at their local computer or enter kinit USER at the command prompt.

The Sync App provides three ways to retrieve the required Kerberos ticket, depending on whether or not the KRB5CCNAME and/or KerberosKeytabFile variables exist in your environment.

MIT Kerberos Credential Cache File

This option enables you to use the MIT Kerberos Ticket Manager or kinit command to get tickets. With this option there is no need to set the User or Password connection properties.

This option requires that KRB5CCNAME has been created in your system.

To enable ticket retrieval via MIT Kerberos Credential Cache Files:

1. Ensure that the KRB5CCNAME variable is present in your environment.
2. Set KRB5CCNAME to a path that points to your credential cache file. (For example, C:\krb_cache\krb5cc_0 or /tmp/krb5cc_0.) The credential cache file is created when you use the MIT Kerberos Ticket Manager to generate your ticket.
3. To obtain a ticket:
   1. Open the MIT Kerberos Ticket Manager application.
   2. Click Get Ticket.
   3. Enter your principal name and password.
   4. Click OK.

   If the ticket is successfully obtained, the ticket information appears in Kerberos Ticket Manager and is stored in the credential cache file.

The Sync App uses the cache file to obtain the Kerberos ticket to connect to Microsoft Dynamics GP.

Note: If you would prefer not to edit KRB5CCNAME, you can use the KerberosTicketCache property to set the file path manually. After this is set, the Sync App uses the specified cache file to obtain the Kerberos ticket to connect to Microsoft Dynamics GP.

Keytab File

If your environment lacks the KRB5CCNAME environment variable, you can retrieve a Kerberos ticket using a Keytab File.

To use this method, set the User property to the desired username, and set the KerberosKeytabFile property to a file path pointing to the keytab file associated with the user.

User and Password

If your environment lacks the KRB5CCNAME environment variable and the KerberosKeytabFile property has not been set, you can retrieve a ticket using a user and password combination.

To use this method, set the User and Password properties to the user/password combination that you use to authenticate with Microsoft Dynamics GP.

Enabling Cross-Realm Authentication

More complex Kerberos environments can require cross-realm authentication where multiple realms and KDC servers are used. For example, they might use one realm/KDC for user authentication, and another realm/KDC for obtaining the service ticket.

To enable this kind of cross-realm authentication, set the KerberosRealm and KerberosKDC properties to the values required for user authentication. Also, set the KerberosServiceRealm and KerberosServiceKDC properties to the values required to obtain the service ticket.

This section details a selection of advanced features of the Microsoft Dynamics GP Sync App.

User Defined Views

The Sync App supports the use of user defined views, virtual tables whose contents are decided by a pre-configured user defined query. These views are useful when you cannot directly control queries being issued to the drivers. For an overview of creating and configuring custom views, see User Defined Views .

SSL Configuration

Use SSL Configuration to adjust how Sync App handles TLS/SSL certificate negotiations. You can choose from various certificate formats;. For further information, see the SSLServerCert property under "Connection String Options" .

Firewall and Proxy

Configure the Sync App for compliance with Firewall and Proxy, including Windows proxies and HTTP proxies. You can also set up tunnel connections.

Query Processing

The Sync App offloads as much of the SELECT statement processing as possible to Microsoft Dynamics GP and then processes the rest of the query in memory (client-side).

For further information, see Query Processing.

Logging

For an overview of configuration settings that can be used to refine CData logging, see Logging. Only two connection properties are required for basic logging, but there are numerous features that support more refined logging, which enables you to use the LogModules connection property to specify subsets of information to be logged.

Customizing the SSL Configuration

By default, the Sync App attempts to negotiate TLS with the server. The server certificate is validated against the default system trusted certificate store. You can override how the certificate gets validated using the SSLServerCert connection property.

To specify another certificate, see the SSLServerCert connection property.

Connecting Through a Firewall or Proxy

HTTP Proxies

To authenticate to an HTTP proxy, set the following:

• ProxyServer: the hostname or IP address of the proxy server that you want to route HTTP traffic through.
• ProxyPort: the TCP port that the proxy server is running on.
• ProxyAuthScheme: the authentication method the Sync App uses when authenticating to the proxy server.
• ProxyUser: the username of a user account registered with the proxy server.
• ProxyPassword: the password associated with the ProxyUser.

Other Proxies

Set the following properties:

• To use a proxy-based firewall, set FirewallType, FirewallServer, and FirewallPort.
• To tunnel the connection, set FirewallType to TUNNEL.
• To authenticate, specify FirewallUser and FirewallPassword.
• To authenticate to a SOCKS proxy, additionally set FirewallType to SOCKS5.

The CData Sync App models Microsoft Dynamics GP entities in relational views, or read-only tables. The tables are determined automatically based on the metadata the Sync App retrieves when you connect. Any changes that you make to your Microsoft Dynamics GP account, such as creating a custom field or changing its data type, are reflected on reconnection.

Views shows some sample view definitions included in the Microsoft Dynamics GP development environment. The actual views available will depend on your account.

Executing Inserts

Some of the entities which are exposed as tables support insert operations. For example to insert a new Customer into the Customer table we execute the following query:

  INSERT INTO Customer (Id, Name, Comment1, Comment2) VALUES ('TEST_CST', 'Name', 'Comment1', 'Comment2')

Executing Inserts using Temporary Tables

While inserting you may encounter columns which end with "Aggregate" keyword. These columns will accept only temporary table values. If using temporary tables, they must be defined and inserted within the same connection. Closing the connection will clear out any temporary tables in memory. For example while inserting a new SalesInvoice the sales lines need to be inserted as well. The sales lines are exposed in SalesInvoice table as the column LinesAggregate. First we have to find the child view that corresponds to the LinesAggregate column. In this case the view is SalesInvoiceLines. Using the view name for our temporary table and its columns as a reference to the sales lines attributes, we will first insert the sales lines to the temporary table. Follow the sql queries below:

  INSERT INTO SalesInvoiceLines#TEMP (LinesItemId, LinesWarehouseId, LinesQuantity, LinesUnitPrice, LinesUnitPriceCurrency) VALUES ('100XLG', 'WAREHOUSE', '1', '30', 'USD')
  INSERT INTO SalesInvoiceLines#TEMP (LinesItemId, LinesWarehouseId, LinesQuantity, LinesUnitPrice, LinesUnitPriceCurrency) VALUES ('M1700', 'WAREHOUSE', '1', '30', 'USD')

  INSERT INTO SalesInvoice (BatchId, CustomerId, DocumentTypeKeyType, DocumentTypeId, LinesAggregate) VALUES ('CONTRACTS', 'PLAZAONE0001', 'Invoice', 'STDINV' , 'SalesInvoiceLines#TEMP')

First we add 2 sales lines into the temporary table with name "SalesInvoiceLines#TEMP". Then we are able to create a new SalesInvoice using the temporary table name as a value for the column LinesAggregate. Note: The columns LinesItemId, LinesWarehouseId, LinesQuantity, LinesUnitPrice, LinesUnitPriceCurrency in the example above have to correspond to real columns in the child table otherwise it will not work.

Below you can find other query examples with or without using temp tables.

  INSERT INTO Customer (Id, Name) VALUES ('TEST_CST', 'Name')

  INSERT INTO CustomerAddress (SalespersonId, SalesTerritoryId, Id, KeyCustomerId, Line1, Line2, City, State, CountryRegion, Fax, Phone1, Phone2, PostalCode) VALUES ('PAUL W.', 'TERRITORY 1', 'WAREHOUSE', 'TEST_CST', '11403 45 St. South', 'Billing Dept.', 'Chicago', 'IL', 'USA', '31255501010000', '42555501010000', '00000000000000', '98052-6399')

  INSERT INTO Vendor (Id, Name, Comment1, Comment2) VALUES ('test11', 'Name', 'Comment1', 'Comment2')

  INSERT INTO VendorAddress (SalespersonId, SalesTerritoryId, Id, KeyVendorId, Line1, Line2, City, State, CountryRegion, Fax, Phone1, Phone2, PostalCode) VALUES ('PAUL W.', 'TERRITORY 1', 'PRIMARY', 'test11', '11403 45 St. South', 'Billing Dept.', 'Chicago', 'IL', 'USA', '31255501010000', '42555501010000', '00000000000000', '98052-6399')

  INSERT INTO PayablesCreditMemo (BatchId, Id, VendorId, PurchaseAmount, PurchaseAmountCurrency, VendorDocumentNumber) VALUES ('JAN-98', 'DM6502', 'CENTRALC0001',  '100', 'USD', 'DOCUMENT 42')

  INSERT INTO ApplicantApplications#TEMP (ApplicationsDateApplied, ApplicationsLastModifiedDate) VALUES ('2021-01-07T00:00:00+01:00','2021-01-07T00:00:00+01:00')
  INSERT INTO Applicant (FirstName, LastName, ApplicationsAggregate) VALUES ('Test', 'Applicant', 'ApplicantApplications#TEMP')

  INSERT INTO PurchaseOrderLines#TEMP (LinesQuantityOrdered, LinesVendorItemNumber, LinesWarehouseId) VALUES ('1', '100XLG', 'WAREHOUSE')
  INSERT INTO PurchaseOrder (LinesAggregate, Id, VendorId) VALUES ('PurchaseOrderLines#TEMP', 'PO4056', 'ACETRAVE0001')

  INSERT INTO SalesReturnLines#TEMP (LinesItemId, LinesWarehouseId, LinesQuantity, LinesUnitPrice, LinesUnitPriceCurrency) VALUES ('100XLG', 'WAREHOUSE', '1', '30', 'USD');
  INSERT INTO SalesReturnLines#TEMP (LinesItemId, LinesWarehouseId, LinesQuantity, LinesUnitPrice, LinesUnitPriceCurrency) VALUES ('M1700', 'WAREHOUSE', '1', '30', 'USD');
  INSERT INTO SalesReturn (BatchId, CustomerId, DocumentTypeKeyType, DocumentTypeId, LinesAggregate) VALUES ('SALES RETURNS', 'PLAZAONE0001', 'Return', 'RTN' , 'SalesReturnLines#TEMP');

Executing Delete

Some of the entities which are exposed as tables support delete operations. For example to delete a Customer from the Customer table we execute the following query:

  DELETE FROM Customer WHERE Id='TEST_CST'

Executing Delete using multiple keys

Some delete operations require multiple keys in order for the query to be successful. For example to delete a CustomerAddress from the CustomerAddresses table requires both key columns the Id and the KeyCustomerId values to be set for ex:

  DELETE FROM CustomerAddress WHERE Id='WAREHOUSE' AND KeyCustomerId='TEST2'

Below you can find other query examples with or without multiple keys.

  DELETE FROM Applicant WHERE ApplicantId='2'

  DELETE FROM SalesInvoice WHERE Id='STDINV2262'

  DELETE FROM ApplicantApplication WHERE ApplicantApplicationKeyApplicantId='3' AND ApplicantApplicationKeySequenceId='1'

Executing Update

Some of the entities which are exposed as tables support update operations. For example to update a Customer from the Customer table we execute the following query:

  UPDATE Customer SET Name='new test name',Comment1='new comment 1', Comment2='new comment 2' WHERE Id='TEST1'

Executing Update using multiple keys

Some update operations require multiple keys in order for the query to be successful. For example to update a CustomerAddress from the CustomerAddresses table requires both key columns the Id and the KeyCustomerId values to be set for ex:

  UPDATE CustomerAddress SET Line1='new line 1', Line2='new line 2', City='new city', State='new state', Fax='111111111', Phone1='222222222', Phone2='3333333', PostalCode='235-325' WHERE KeyCustomerId='TEST1234' AND Id='WAREHOUSE'

  UPDATE SalesInvoice SET CustomerId='AARONFIT0001', Date='2021-01-07T00:00:00+01:00' WHERE Id='STDINV2300' AND BatchId='CONTRACTS'

Note: When updating the tables SalesInvoice, SalesOrder, SalesQuote, SalesReturn, SalesBackorder, SalesFulfillmentOrder the Date column should be set for a successful query.

Executing Update using temporary tables

As explained in Executing Inserts using Temporary Tables the temporary tables can also be used in update operations. Take a look at the query below which updates the quantity of the existing items in our invoice:

  INSERT INTO SalesInvoiceLines#TEMP (LinesItemId, LinesWarehouseId, LinesQuantity, LinesUnitPrice, LinesUnitPriceCurrency) VALUES ('100XLG', 'WAREHOUSE', '2', '30', 'USD')
  INSERT INTO SalesInvoiceLines#TEMP (LinesItemId, LinesWarehouseId, LinesQuantity, LinesUnitPrice, LinesUnitPriceCurrency) VALUES ('M1700', 'WAREHOUSE', '2', '30', 'USD')

  UPDATE SalesInvoice SET Date='2021-01-07T00:00:00+01:00', LinesAggregate='SalesInvoiceLines#TEMP' WHERE Id='STDINV2300' AND BatchId='CONTRACTS'

Below you can find other query examples.

  UPDATE SalesOrder SET CustomerId='AARONFIT0001', Date='2021-01-07T00:00:00+01:00' WHERE Id='ORDST2225' AND BatchId='SOP ORDERS'

  INSERT INTO ApplicantApplications#TEMP (ApplicationsDateApplied, ApplicationsLastModifiedDate) VALUES ('2021-01-05T00:00:00+01:00','2021-01-07T00:00:00+01:00')
  UPDATE Applicant SET FirstName='New Test Name', LastName='New Applicant Name', ApplicationsAggregate='ApplicantApplications#TEMP' WHERE ApplicantId='3'

  UPDATE SalesQuote SET CustomerId='BAKERSEM0001', Date='2021-01-07T00:00:00+01:00' WHERE Id='QTEST1022' AND BatchId='SALES QUOTES'

  UPDATE Vendor SET Name='new test name',Comment1='new comment 1', Comment2='new comment 2' WHERE Id='ACETRAVE0001'

  UPDATE VendorAddress SET Line1='new line 1', Line2='new line 2', City='new city', State='new state', Fax='111111111', Phone1='222222222', Phone2='3333333', PostalCode='235-325' WHERE KeyVendorId='ACETRAVE0001' AND Id='PRIMARY'

The Sync App models the data in Microsoft Dynamics GP as a list of tables in a relational database that can be queried using standard SQL statements.

Microsoft Dynamics GP Connector for CData Sync Tables

Name	Description
Applicant	Return a list of: Applicant
ApplicantEducation	Return a list of: ApplicantEducation
ApplicantInterview	Return a list of: ApplicantInterview
ApplicantReference	Return a list of: ApplicantReference
ApplicantSkill	Return a list of: ApplicantSkill
ApplicantTest	Return a list of: ApplicantTest
ApplicantWorkHistory	Return a list of: ApplicantWorkHistory
BackOfficeRoleAssignment	Return a list of: BackOfficeRoleAssignment
BusinessObjectUserAssignment	Return a list of: BusinessObjectUserAssignment
CashReceipt	Return a list of: CashReceipt
Customer	Return a list of: Customer
CustomerAddress	Return a list of: CustomerAddress
Employee	Return a list of: Employee
EmployeeAddress	Return a list of: EmployeeAddress
EmployeePayCode	Return a list of: EmployeePayCode
Fee	Return a list of: Fee
GLFixedAllocationAccount	Return a list of: GLFixedAllocationAccount
GLPostingAccount	Return a list of: GLPostingAccount
GLTransaction	Return a list of: GLTransaction
GLUnitAccount	Return a list of: GLUnitAccount
GLVariableAllocationAccount	Return a list of: GLVariableAllocationAccount
HRRequisition	Return a list of: HRRequisition
InventoryAdjustment	Return a list of: InventoryAdjustment
InventoryTransfer	Return a list of: InventoryTransfer
InventoryVariance	Return a list of: InventoryVariance
ItemCurrency	Return a list of: ItemCurrency
ItemVendor	Return a list of: ItemVendor
ItemWarehouse	Return a list of: ItemWarehouse
PayablesCreditMemo	Return a list of: PayablesCreditMemo
PayablesFinanceCharge	Return a list of: PayablesFinanceCharge
PayablesInvoice	Return a list of: PayablesInvoice
PayablesMiscellaneousCharge	Return a list of: PayablesMiscellaneousCharge
PayablesReturn	Return a list of: PayablesReturn
Policy	Return a list of: Policy
Pricing	Return a list of: Pricing
PurchaseInvoice	Return a list of: PurchaseInvoice
PurchaseOrder	Return a list of: PurchaseOrder
PurchaseReceipt	Return a list of: PurchaseReceipt
ReceivablesCreditMemo	Return a list of: ReceivablesCreditMemo
ReceivablesDebitMemo	Return a list of: ReceivablesDebitMemo
ReceivablesFinanceCharge	Return a list of: ReceivablesFinanceCharge
ReceivablesInvoice	Return a list of: ReceivablesInvoice
ReceivablesReturn	Return a list of: ReceivablesReturn
ReceivablesServiceRepair	Return a list of: ReceivablesServiceRepair
ReceivablesWarranty	Return a list of: ReceivablesWarranty
ReturnMaterialAuthorization	Return a list of: ReturnMaterialAuthorization
SalesBackorder	Return a list of: SalesBackorder
SalesFulfillmentOrder	Return a list of: SalesFulfillmentOrder
SalesInvoice	Return a list of: SalesInvoice
SalesOrder	Return a list of: SalesOrder
SalesProcessHoldSetup	Return a list of: SalesProcessHoldSetup
SalesQuote	Return a list of: SalesQuote
SalesReturn	Return a list of: SalesReturn
Service	Return a list of: Service
ServiceCall	Return a list of: ServiceCall
ServiceEquipment	Return a list of: ServiceEquipment
ServiceQuote	Return a list of: ServiceQuote
Skill	Return a list of: Skill
SkillSet	Return a list of: SkillSet
Vendor	Return a list of: Vendor
VendorAddress	Return a list of: VendorAddress
Warehouse	Return a list of: Warehouse

Return a list of: Applicant

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
AddressExtensionsExtensionAggregate	String	False
AddressCity	String	False
AddressLine1	String	False
AddressLine2	String	False
AddressLine3	String	False
AddressPostalCode	String	False
AddressState	String	False
AddressCountryRegion	String	False
AddressFaxCountryCode	String	False
AddressFaxExtension	String	False
AddressFax	String	False
AddressPhone1CountryCode	String	False
AddressPhone1Extension	String	False
AddressPhone1	String	False
AddressPhone2CountryCode	String	False
AddressPhone2Extension	String	False
AddressPhone2	String	False
AddressPhone3CountryCode	String	False
AddressPhone3Extension	String	False
AddressPhone3	String	False
AgeCode	String	False
ApplicantId [KEY]	Int	False
ApplicationColorColorCode	String	False
ApplicationColorColorName	String	False
ApplicationStatus	String	False
ApplicationsAggregate	String	False
CompanyCode	String	False
DateApplied	Datetime	False
DepartmentId	String	False
DivisionId	String	False
Ethnicity	String	False
FirstName	String	False
Gender	String	False
HRRequisistionId	String	False
InterviewsAggregate	String	False
IsDisabled	Bool	False
IsDisabledVeteran	Bool	False
IsOtherVeteran	Bool	False
IsReplyLetterSent	Bool	False
IsVeteran	Bool	False
IsVietnamEraVeteran	Bool	False
IsWillRelocate	Bool	False
LastModifiedBy	String	False
LastModifiedDate	Datetime	False
LastName	String	False
Location	String	False
MiddleName	String	False
PositionId	String	False
PreviousEmployersAggregate	String	False
ReferenceInformationSource	String	False
ReferenceInformationSourceDescription	String	False
ReferencesAggregate	String	False
RejectionInformationComment	String	False
RejectionInformationReason	String	False
SchoolsAggregate	String	False
SequenceId	Int	False
SkillsAggregate	String	False
TaxIdentifier	String	False
TestsAggregate	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: ApplicantEducation

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
ApplicantEducationKeyApplicantId [KEY]	Int	False
ApplicantEducationKeySequenceId [KEY]	Int	False
Degree	String	False
DeleteOnUpdate	Bool	False
GPABase	String	False
GradePointAverage	String	False
LastModifiedBy	String	False
LastModifiedDate	Datetime	False
Major	String	False
Notes	String	False
School	String	False
YearGraduated	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: ApplicantInterview

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
ApplicantInterviewKeyApplicantId [KEY]	Int	False
ApplicantInterviewKeyApplyDateId [KEY]	Datetime	False
ApplicantInterviewKeyInterviewTypeId [KEY]	String	False
CompanyCode	String	False
DeleteOnUpdate	Bool	False
DepartmentId	String	False
DivisionId	String	False
EffectiveDate	Datetime	False
InterviewItemsAggregate	String	False
InterviewTypeCode	Int	False
Notes	String	False
PositionId	String	False
ReviewRange	Int	False
ReviewRating	Decimal	False
TotalWeight	Int	False
WeightedScore	Int	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: ApplicantReference

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
AddressExtensionsExtensionAggregate	String	False
AddressCity	String	False
AddressLine1	String	False
AddressLine2	String	False
AddressLine3	String	False
AddressPostalCode	String	False
AddressState	String	False
AddressCountryRegion	String	False
AddressFaxCountryCode	String	False
AddressFaxExtension	String	False
AddressFax	String	False
AddressPhone1CountryCode	String	False
AddressPhone1Extension	String	False
AddressPhone1	String	False
AddressPhone2CountryCode	String	False
AddressPhone2Extension	String	False
AddressPhone2	String	False
AddressPhone3CountryCode	String	False
AddressPhone3Extension	String	False
AddressPhone3	String	False
ApplicantReferenceKeyApplicantSequenceKeyApplicantId [KEY]	Int	False
ApplicantReferenceKeyApplicantSequenceKeySequenceId [KEY]	Int	False
ApplicantReferenceId [KEY]	String	False
CompanyName	String	False
DeleteOnUpdate	Bool	False
LastModifiedBy	String	False
LastModifiedDate	Datetime	False
Notes	String	False
Relationship	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: ApplicantSkill

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
ApplicantSkillKeyApplicantId [KEY]	Int	False
ApplicantSkillKeySkillId [KEY]	String	False
Comments	String	False
DeleteOnUpdate	Bool	False
Proficiency	Int	False
SkillNumber	Int	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: ApplicantTest

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
ApplicantTestKeyApplicantSequenceKeyApplicantId [KEY]	Int	False
ApplicantTestKeyApplicantSequenceKeySequenceId [KEY]	Int	False
ApplicantTestKeyTestId [KEY]	String	False
DeleteOnUpdate	Bool	False
LastModifiedBy	String	False
LastModifiedDate	Datetime	False
Notes	String	False
Score	String	False
TestDate	Datetime	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: ApplicantWorkHistory

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
ApplicantWorkHistoryKeyApplicantSequenceKeyApplicantId [KEY]	Int	False
ApplicantWorkHistoryKeyApplicantSequenceKeySequenceId [KEY]	Int	False
ApplicantWorkHistoryId [KEY]	String	False
CompensationPeriod	String	False
DeleteOnUpdate	Bool	False
EndDate	Datetime	False
LastModifiedBy	String	False
LastModifiedDate	Datetime	False
Notes	String	False
PositionId	String	False
StartDate	Datetime	False
Wage	Decimal	False
YearsOfExperience	Int	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: BackOfficeRoleAssignment

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
KeyRoleId [KEY]	String	False
KeyUserId [KEY]	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: BusinessObjectUserAssignment

Columns

Name	Type	ReadOnly	Description
BusinessObjectKey	String	False
BusinessObjectTypeId	String	False
User [KEY]	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: CashReceipt

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
AmountCurrency	String	False
Amount	Decimal	False
AuditTrailCode	String	False
BankAccountId	String	False
BatchKeyCreatedDateTime	Datetime	False
BatchId	String	False
BatchKeySource	String	False
CheckCardNumber	String	False
CorporateAccountId	String	False
CurrencyKeyISOCode	String	False
CustomerId	String	False
Date	Datetime	False
Description	String	False
DistributionsAggregate	String	False
ExchangeDate	Datetime	False
ExchangeRate	Decimal	False
GeneralLedgerPostingDate	Datetime	False
IsVoided	Bool	False
Id [KEY]	String	False
ModifiedBy	String	False
ModifiedDate	Datetime	False
PaymentCardTypeId	String	False
PostedBy	String	False
PostedDate	Datetime	False
Type	String	False
VoidDate	Datetime	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: Customer

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
AccountsReceivableGLAccountId	String	False
AccountsReceivableGLAccountKeyIsEncrypted	Bool	False
AddressesAggregate	String	False
AllowRevaluation	Bool	False
BalanceType	String	False
BankAccountId	String	False
BankBranch	String	False
BankName	String	False
BillToAddressKeyCustomerId	String	False
BillToAddressId	String	False
CashGLAccountId	String	False
CashGLAccountKeyIsEncrypted	Bool	False
ClassId	String	False
Comment1	String	False
Comment2	String	False
CorporateAccountId	String	False
CostOfGoodsSoldGLAccountId	String	False
CostOfGoodsSoldGLAccountKeyIsEncrypted	Bool	False
CreatedDate	Datetime	False
CreditLimitItem	String	False
CreditLimitPeriod	Int	False
CreditLimitPeriodAmountCurrency	String	False
CreditLimitPeriodAmount	Decimal	False
CurrencyKeyISOCode	String	False
DefaultAddressKeyCustomerId	String	False
DefaultAddressId	String	False
DefaultCashAccountType	String	False
DiscountGracePeriod	Int	False
DueDateGracePeriod	Int	False
FinanceChargeItem	String	False
FinanceChargesGLAccountId	String	False
FinanceChargesGLAccountKeyIsEncrypted	Bool	False
HistoryOptionsKeepCalendarHistory	Bool	False
HistoryOptionsKeepDistributionHistory	Bool	False
HistoryOptionsKeepFiscalHistory	Bool	False
HistoryOptionsKeepTransactionHistory	Bool	False
IncludeInDemandPlanning	Bool	False
InventoryGLAccountId	String	False
InventoryGLAccountKeyIsEncrypted	Bool	False
IsActive	Bool	False
IsOnHold	Bool	False
Id [KEY]	String	False
LastModifiedDate	Datetime	False
MaximumWriteoffItem	String	False
MinimumPaymentItem	String	False
ModifiedDate	Datetime	False
Name	String	False
Notes	String	False
OrderFullfillmentShortageDefault	String	False
OverpaymentWriteoffGLAccountId	String	False
OverpaymentWriteoffGLAccountKeyIsEncrypted	Bool	False
PaymentCardAccountExpirationDate	Datetime	False
PaymentCardAccountKeyNumber	String	False
PaymentCardAccountKeyPaymentCardTypeId	String	False
PaymentTermsDiscountAvailableGLAccountId	String	False
PaymentTermsDiscountAvailableGLAccountKeyIsEncrypted	Bool	False
PaymentTermsDiscountTakenGLAccountId	String	False
PaymentTermsDiscountTakenGLAccountKeyIsEncrypted	Bool	False
PaymentTermsId	String	False
PostResultsTo	String	False
PriceLevelId	String	False
Priority	Int	False
RateTypeId	String	False
SalesGLAccountId	String	False
SalesGLAccountKeyIsEncrypted	Bool	False
SalesOrderReturnsGLAccountId	String	False
SalesOrderReturnsGLAccountKeyIsEncrypted	Bool	False
SendEmailStatements	Bool	False
ShipCompleteOnly	Bool	False
ShipToAddressKeyCustomerId	String	False
ShipToAddressId	String	False
Shortname	String	False
StatementCycle	String	False
StatementName	String	False
StatementRecipientsBCCAggregate	String	False
StatementRecipientsCCAggregate	String	False
StatementRecipientsToAggregate	String	False
StatementToAddressKeyCustomerId	String	False
StatementToAddressId	String	False
TaxExemptNumbersAggregate	String	False
TaxRegistrationNumber	String	False
TradeDiscountPercent	Decimal	False
UserDefined1	String	False
UserDefined2	String	False
UserLanguageId	Int	False
WriteoffGLAccountId	String	False
WriteoffGLAccountKeyIsEncrypted	Bool	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: CustomerAddress

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
City	String	False
Line1	String	False
Line2	String	False
Line3	String	False
PostalCode	String	False
State	String	False
CountryRegion	String	False
FaxCountryCode	String	False
FaxExtension	String	False
Fax	String	False
Phone1CountryCode	String	False
Phone1Extension	String	False
Phone1	String	False
Phone2CountryCode	String	False
Phone2Extension	String	False
Phone2	String	False
Phone3CountryCode	String	False
Phone3Extension	String	False
Phone3	String	False
CountryRegionCodeId	String	False
ContactPerson	String	False
Name	String	False
CreatedDate	Datetime	False
InternetAddressesAdditionalInformation	String	False
InternetAddressesEmailBccAddress	String	False
InternetAddressesEmailCcAddress	String	False
InternetAddressesEmailToAddress	String	False
InternetAddressesInternetField1	String	False
InternetAddressesInternetField2	String	False
InternetAddressesInternetField3	String	False
InternetAddressesInternetField4	String	False
InternetAddressesInternetField5	String	False
InternetAddressesInternetField6	String	False
InternetAddressesInternetField7	String	False
InternetAddressesInternetField8	String	False
InternetAddressesMessengerAddress	String	False
LastModifiedDate	Datetime	False
ModifiedDate	Datetime	False
ShippingMethodId	String	False
TaxScheduleId	String	False
UPSZone	String	False
UserDefined1	String	False
UserDefined2	String	False
DeleteOnUpdate	Bool	False
KeyCustomerId [KEY]	String	False
Id [KEY]	String	False
SalesTerritoryId	String	False
SalespersonId	String	False
WarehouseId	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: Employee

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
AddressesAggregate	String	False
BenefitExpiration	Datetime	False
BenefitStartDate	Datetime	False
BirthDate	Datetime	False
ClassId	String	False
CompanyAddressId	String	False
DayOfBirth	Int	False
DefaultAddressKeyEmployeeId	String	False
DefaultAddressId	String	False
DefaultCashAccountFromType	String	False
DepartmentId	String	False
DivisionId	String	False
DoesCalculateMinimumWageBalance	Bool	False
EmployeeInactivatedDate	Datetime	False
EmployeeId [KEY]	String	False
EmploymentStartDate	Datetime	False
EmploymentType	String	False
Ethnicity	String	False
FederalClass	String	False
GLAccountId	String	False
GLAccountKeyIsEncrypted	Bool	False
GenderCode	String	False
HRStatus	String	False
I9RenewDate	Datetime	False
IsActive	Bool	False
IsDisabled	Bool	False
IsDisabledVeteran	Bool	False
IsI9Verified	Bool	False
IsOtherVeteran	Bool	False
IsSmoker	Bool	False
IsUnionEmployee	Bool	False
IsUnitedStatesCitizen	Bool	False
IsVeteran	Bool	False
IsVietnamEraVeteran	Bool	False
LastWorkedDate	Datetime	False
MaritalStatus	String	False
MilitaryDischargeDate	Datetime	False
MinimumNetPayCurrency	String	False
MinimumNetPay	Decimal	False
ModifiedBy	String	False
ModifiedDate	Datetime	False
MonthOfBirth	String	False
NameAlternate	String	False
NameFamily	String	False
NameGiven	String	False
NameMiddle	String	False
NamePreferred	String	False
NameSuffix	String	False
PositionId	String	False
PrimaryPayCodeId	String	False
RateClass	String	False
ReasonEmployeeInactivated	String	False
ReviewLastDate	Datetime	False
ReviewNextDate	Datetime	False
SUTAStateId	String	False
SickTimeAccrualAmount	Decimal	False
SickTimeAccrualMethod	String	False
SickTimeDoesAutomaticallyAccrue	Bool	False
SickTimeHoursAvailable	Decimal	False
SickTimeHoursPerYear	Int	False
SickTimeWarnWhenHoursAvailableFallsBelowZero	Bool	False
SpouseName	String	False
SpouseTaxIdentifier	String	False
Status	String	False
SupervisorId	String	False
TaxIdentifier	String	False
UnionId	String	False
UserDefined1	String	False
UserDefined2	String	False
VacationAccrualAmount	Decimal	False
VacationAccrualMethod	String	False
VacationDoesAutomaticallyAccrue	Bool	False
VacationHoursAvailable	Decimal	False
VacationHoursPerYear	Int	False
VacationWarnWhenHoursAvailableFallsBelowZero	Bool	False
WorkHoursPerYear	Int	False
WorkersCompensationId	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: EmployeeAddress

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
City	String	False
Line1	String	False
Line2	String	False
Line3	String	False
PostalCode	String	False
State	String	False
CountryRegion	String	False
FaxCountryCode	String	False
FaxExtension	String	False
Fax	String	False
Phone1CountryCode	String	False
Phone1Extension	String	False
Phone1	String	False
Phone2CountryCode	String	False
Phone2Extension	String	False
Phone2	String	False
Phone3CountryCode	String	False
Phone3Extension	String	False
Phone3	String	False
CountryRegionCodeId	String	False
County	String	False
DeleteOnUpdate	Bool	False
InternetAddressesAdditionalInformation	String	False
InternetAddressesEmailBccAddress	String	False
InternetAddressesEmailCcAddress	String	False
InternetAddressesEmailToAddress	String	False
InternetAddressesInternetField1	String	False
InternetAddressesInternetField2	String	False
InternetAddressesInternetField3	String	False
InternetAddressesInternetField4	String	False
InternetAddressesInternetField5	String	False
InternetAddressesInternetField6	String	False
InternetAddressesInternetField7	String	False
InternetAddressesInternetField8	String	False
InternetAddressesMessengerAddress	String	False
KeyEmployeeId [KEY]	String	False
Id [KEY]	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: EmployeePayCode

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
ApplicableTaxesIsFederalTaxApplied	Bool	False
ApplicableTaxesIsFutaApplied	Bool	False
ApplicableTaxesIsLocalTaxApplied	Bool	False
ApplicableTaxesIsMedicareApplied	Bool	False
ApplicableTaxesIsSocialSecurityApplied	Bool	False
ApplicableTaxesIsStateTaxApplied	Bool	False
ApplicableTaxesIsSutaApplied	Bool	False
ApplicableTaxesSutaState	String	False
BasePayRecordId	String	False
BasedOnRate	Decimal	False
EmployeePayCodeKeyEmployeeId [KEY]	String	False
EmployeePayCodeKeyPayCodeId [KEY]	String	False
FlatTaxRatesFederal	Decimal	False
FlatTaxRatesState	Decimal	False
IsDataEntry	Bool	False
IsInactive	Bool	False
IsPrimaryPayRecord	Bool	False
IsReportAsWages	Bool	False
IsSickTimeAccrued	Bool	False
IsTaxable	Bool	False
IsVacationAccrued	Bool	False
MaxPayPerPeriod	Decimal	False
Notes	String	False
PayAdvance	Decimal	False
PayAdvanceTaken	Decimal	False
PayFactor	Decimal	False
PayPerPeriod	Decimal	False
PayPeriod	String	False
PayRate	Decimal	False
PayStepBasedOn	String	False
PayStepEffectiveDate	Datetime	False
PayStepPayStepId	String	False
PayStepStep	Int	False
PayStepStepFTE	Decimal	False
PayType	String	False
PayUnit	String	False
PayUnitPeriod	String	False
ShiftCode	String	False
TipType	String	False
W2BoxesLabelsW2BoxLabel1	String	False
W2BoxesLabelsW2BoxLabel2	String	False
W2BoxesLabelsW2BoxLabel3	String	False
W2BoxesLabelsW2BoxLabel4	String	False
W2BoxesLabelsW2BoxNumber1	Int	False
W2BoxesLabelsW2BoxNumber2	Int	False
W2BoxesLabelsW2BoxNumber3	Int	False
W2BoxesLabelsW2BoxNumber4	Int	False
WorkersComp	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: Fee

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
ABCCode	String	False
AllowBackOrder	Bool	False
AssemblyVarianceGLAccountId	String	False
AssemblyVarianceGLAccountKeyIsEncrypted	Bool	False
ClassId	String	False
CostofGoodsSoldGLAccountId	String	False
CostofGoodsSoldGLAccountKeyIsEncrypted	Bool	False
CreatedDate	Datetime	False
CurrencyDecimalPlaces	String	False
CurrentCostCurrency	String	False
CurrentCost	Decimal	False
DamagedGLAccountId	String	False
DamagedGLAccountKeyIsEncrypted	Bool	False
DefaultPriceLevelId	String	False
DefaultSellingUofM	String	False
DefaultWarehouseId	String	False
Description	String	False
DropShipGLAccountId	String	False
DropShipGLAccountKeyIsEncrypted	Bool	False
FunctionalCurrencyDecimalPlaces	String	False
GenericDescription	String	False
InServiceGLAccountId	String	False
InServiceGLAccountKeyIsEncrypted	Bool	False
InUseGLAccountId	String	False
InUseGLAccountKeyIsEncrypted	Bool	False
IncludeInDemandPlanning	Bool	False
InternetAddressesAdditionalInformation	String	False
InternetAddressesEmailBccAddress	String	False
InternetAddressesEmailCcAddress	String	False
InternetAddressesEmailToAddress	String	False
InternetAddressesInternetField1	String	False
InternetAddressesInternetField2	String	False
InternetAddressesInternetField3	String	False
InternetAddressesInternetField4	String	False
InternetAddressesInternetField5	String	False
InternetAddressesInternetField6	String	False
InternetAddressesInternetField7	String	False
InternetAddressesInternetField8	String	False
InternetAddressesMessengerAddress	String	False
InventoryGLAccountId	String	False
InventoryGLAccountKeyIsEncrypted	Bool	False
InventoryOffsetGLAccountId	String	False
InventoryOffsetGLAccountKeyIsEncrypted	Bool	False
InventoryReturnGLAccountId	String	False
InventoryReturnGLAccountKeyIsEncrypted	Bool	False
IsDiscontinued	Bool	False
KeepCalendarYearHistory	Bool	False
KeepDistributionHistory	Bool	False
KeepFiscalYearHistory	Bool	False
KeepTransactionHistory	Bool	False
Id [KEY]	String	False
LastModifiedDate	Datetime	False
MarkdownGLAccountId	String	False
MarkdownGLAccountKeyIsEncrypted	Bool	False
ModifiedDate	Datetime	False
PriceMethod	String	False
PurchasePriceVarianceGLAccountId	String	False
PurchasePriceVarianceGLAccountKeyIsEncrypted	Bool	False
PurchaseTaxBasis	String	False
PurchaseTaxScheduleId	String	False
PurchaseUofM	String	False
QuantityDecimalPlaces	String	False
SalesGLAccountId	String	False
SalesGLAccountKeyIsEncrypted	Bool	False
SalesReturnGLAccountId	String	False
SalesReturnGLAccountKeyIsEncrypted	Bool	False
SalesTaxBasis	String	False
SalesTaxScheduleId	String	False
ShippingWeight	Decimal	False
ShortDescription	String	False
StandardCostCurrency	String	False
StandardCost	Decimal	False
SubstituteItem1Id	String	False
SubstituteItem2Id	String	False
Type	String	False
UnrealizedPurchasePriceVarianceGLAccountId	String	False
UnrealizedPurchasePriceVarianceGLAccountKeyIsEncrypted	Bool	False
UofMScheduleId	String	False
UserCategoryList1	String	False
UserCategoryList2	String	False
UserCategoryList3	String	False
UserCategoryList4	String	False
UserCategoryList5	String	False
UserCategoryList6	String	False
VarianceGLAccountId	String	False
VarianceGLAccountKeyIsEncrypted	Bool	False
WarrantyDays	Short	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: GLFixedAllocationAccount

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
Alias	String	False
CreatedDate	Datetime	False
Description	String	False
IsActive	Bool	False
Id [KEY]	String	False
KeyIsEncrypted [KEY]	Bool	False
ModifiedDate	Datetime	False
Type	String	False
PostInventoryIn	String	False
PostPayrollIn	String	False
PostPurchasingIn	String	False
PostSalesIn	String	False
DistributionsAggregate	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: GLPostingAccount

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
Alias	String	False
CreatedDate	Datetime	False
Description	String	False
IsActive	Bool	False
Id [KEY]	String	False
KeyIsEncrypted [KEY]	Bool	False
ModifiedDate	Datetime	False
Type	String	False
PostInventoryIn	String	False
PostPayrollIn	String	False
PostPurchasingIn	String	False
PostSalesIn	String	False
AllowAccountEntry	Bool	False
CurrenciesAggregate	String	False
GLAccountCategoryId	String	False
IsRevalued	Bool	False
PostRevaluationResultsTo	String	False
PostingType	String	False
RevaluationMethod	String	False
TypicalBalance	String	False
UserDefined1	String	False
UserDefined2	String	False
UserDefined3	String	False
UserDefined4	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: GLTransaction

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
AuditTrailCode	String	False
BatchKeyCreatedDateTime	Datetime	False
BatchId	String	False
BatchKeySource	String	False
CurrencyKeyISOCode	String	False
ExchangeDate	Datetime	False
ExchangeRate	Decimal	False
IntercompanyId	Int	False
IntercompanyOriginalJournalId	Int	False
IsVoided	Bool	False
KeyDate [KEY]	Datetime	False
KeyJournalId [KEY]	Int	False
LedgerType	String	False
LinesAggregate	String	False
ModifiedBy	String	False
ModifiedDate	Datetime	False
OriginatingDocumentAuditTrailCode	String	False
OriginatingDocumentPostedDate	Datetime	False
OriginatingDocumentSeries	String	False
PostedBy	String	False
Reference	String	False
SourceDocumentId	String	False
TransactionState	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: GLUnitAccount

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
Alias	String	False
CreatedDate	Datetime	False
Description	String	False
IsActive	Bool	False
Id [KEY]	String	False
KeyIsEncrypted [KEY]	Bool	False
ModifiedDate	Datetime	False
Type	String	False
DecimalPlaces	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: GLVariableAllocationAccount

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
Alias	String	False
CreatedDate	Datetime	False
Description	String	False
IsActive	Bool	False
Id [KEY]	String	False
KeyIsEncrypted [KEY]	Bool	False
ModifiedDate	Datetime	False
Type	String	False
PostInventoryIn	String	False
PostPayrollIn	String	False
PostPurchasingIn	String	False
PostSalesIn	String	False
BalanceForCalculation	String	False
DistributionsAggregate	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: HRRequisition

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
AdvertisingListLine1	String	False
AdvertisingListLine2	String	False
AdvertisingListLine3	String	False
AdvertisingListLine4	String	False
AdvertisingListLine5	String	False
ApplicantsApplied	Int	False
ApplicantsInterviewed	Int	False
CompanyCode	String	False
DepartmentId	String	False
DivisionId	String	False
InternalCloseDate	Datetime	False
InternalPostDate	Datetime	False
JobPostingType	String	False
LastModifiedBy	String	False
LastModifiedDate	Datetime	False
ManagerId	String	False
OpeningDate	Datetime	False
PositionId	String	False
PositionsAvailable	Int	False
PositionsFilled	Int	False
Recruiter	String	False
RequisitionCostsAdvertising	Decimal	False
RequisitionCostsLodging	Decimal	False
RequisitionCostsMovingExpenses	Decimal	False
RequisitionCostsOther	Decimal	False
RequisitionCostsRecruiterFees	Decimal	False
RequisitionCostsTravel	Decimal	False
RequisitionNumberId [KEY]	String	False
Status	String	False
SupervisorId	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: InventoryAdjustment

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
AuditTrailCode	String	False
BatchKeyCreatedDateTime	Datetime	False
BatchId	String	False
BatchKeySource	String	False
CreatedDate	Datetime	False
Date	Datetime	False
GLPostingDate	Datetime	False
Id [KEY]	String	False
ModifiedDate	Datetime	False
TransactionState	String	False
LinesAggregate	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: InventoryTransfer

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
AuditTrailCode	String	False
BatchKeyCreatedDateTime	Datetime	False
BatchId	String	False
BatchKeySource	String	False
CreatedDate	Datetime	False
Date	Datetime	False
GLPostingDate	Datetime	False
Id [KEY]	String	False
ModifiedDate	Datetime	False
TransactionState	String	False
LinesAggregate	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: InventoryVariance

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
AuditTrailCode	String	False
BatchKeyCreatedDateTime	Datetime	False
BatchId	String	False
BatchKeySource	String	False
CreatedDate	Datetime	False
Date	Datetime	False
GLPostingDate	Datetime	False
Id [KEY]	String	False
ModifiedDate	Datetime	False
TransactionState	String	False
LinesAggregate	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: ItemCurrency

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
CurrencyDecimalPlaces	String	False
KeyCurrencyKeyISOCode [KEY]	String	False
KeyItemId [KEY]	String	False
ListPriceCurrency	String	False
ListPrice	Decimal	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: ItemVendor

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
AverageLeadTime	Decimal	False
EconomicOrderQuantity	Decimal	False
FreeOnBoard	String	False
KeyItemId [KEY]	String	False
KeyVendorId [KEY]	String	False
LastCurrencyKeyISOCode	String	False
LastOriginatingCostCurrency	String	False
LastOriginatingCost	Decimal	False
MaximumOrderQuantity	Decimal	False
MinimumOrderQuantity	Decimal	False
NumberOfReceipts	Short	False
OrderMultipleQuantity	Decimal	False
PlanningLeadTime	Short	False
PurchasingUofM	String	False
RequisitionedQuantity	Decimal	False
VendorItemDescription	String	False
VendorItemNumber	String	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String

Return a list of: ItemWarehouse

Columns

Name	Type	ReadOnly	Description
ExtensionsExtensionAggregate	String	False
Bin	String	False
BuyerId	String	False
KeyItemId [KEY]	String	False
KeyWarehouseId [KEY]	String	False
LandedCostGroupId	String	False
PlannerId	String	False
PlanningFixedOrderQuantity	Decimal	False
PlanningManufacturingLeadTime	Decimal	False
PlanningMaximumOrderQuantity	Decimal	False
PlanningMinimumOrderQuantity	Decimal	False
PlanningOrderMultipleQuantity	Decimal	False
PlanningOrderPointQuantity	Decimal	False
PlanningOrderPolicy	String	False
PlanningOrderUpToLevelQuantity	Decimal	False
PlanningPurchasingLeadTime	Decimal	False
PlanningReorderVarianceQuantity	Decimal	False
PlanningReplenishmentMethod	String	False
PlanningSafetyStockQuantity	Decimal	False
PlanningShrinkageFactor	Decimal	False
PlanningTimeFence	Short	False
PrimaryVendorId	String	False
RequisitionedQuantity	Decimal	False

Pseudo-Columns

Pseudo-Column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.

Name	Type	Description
PagingColumn	String