...
File Name Rules for More Complex Related Record Types
The following Related Record Types have composite RelatedRecordID's
- CashFlow
- Forecast
- SubContractorCetrtificationDetail
- Timesheet
This means these Related Record Types have RelatedRecordID's that are made up of more than one part. When this happens the RelatedRecordID's parts are sepreated by a dot (.) (period or fullstop).
Some Example file names are:
Cashflow or Forecast: A pdf file to be attached to JobCode ABC123 Year 2000 Period 9, with a group name of 'Default Group' and a Description of 'Graph' would be named:
ABC123.2000.9;Default Group;Graph.pdf
Timesheet: A csv file to be attached to PersonID 1234 Timesheet Weekending Date 09/11/2012 , with no group name specified and a Description of 'Hours Worked' would be named:
1234.2000119;;Hours Worked.csv
The table below identifies what each part is and in the case of timesheets the format.
What RelatedRecordID is used for my file type?
...
| Record Type | RelatedRecordID format | Table Validated Against | |
|---|---|---|---|
| Action | ActionID | Actions | |
| APCredit | APInvoiceID | APInvoices | |
| APInvoice | APInvoiceID | APInvoices | |
| APVoucher | VoucherID | APVoucher | |
| ARCredit | InvoiceNumber | JobInvoices | |
| ARInvoice | InvoiceNumber | JobInvoices | |
| Asset | AssetID | Assets | |
| Batch | BatchNo | BatchHeaders | |
| CashFlow | JobCode.YearNo.PeriodNo | Forecasts | |
| Company | CompanyID | Companies | |
| Contract | ContractCode | Contracts | |
| Drawing | DocID | Documents | |
| Estimate | EstimateID | Estimates | |
| Forecast | JobCode.YearNo.PeriodNo | Forecasts | |
| ForecastGainAndLoss | WIPAdjustmentID | WIPAdjustments | |
| ForecastRiskAdjustment | ForecastRiskID | ForecastRisk | |
| ForecastSubcontractRisk | ForecastRiskID | ForecastRisk | |
| ForecastUncommittedAdjustment | ForecastRiskID | ForecastRisk | |
| ForecastWIPAdjustment | WIPAdjustmentID | WIPAdjustments | |
| Item | ItemID | Items | |
| Job | Jobs | JobCode | |
| JobTransaction | JobTranID | JobTransactions | |
| Meeting | MeetingID | Meetings | |
| MeetingItem | MeetingItemID | MeetingItems | |
| Person | PersonID | People | |
| Plant | JobCode | Jobs | |
| PlantPolicy | QuoteID | PlantPolicy | |
| PlantServiceOrder | QuoteID | PlantServiceOrders | |
| PriceRequest | PriceRequestID | PriceRequestHeader | |
| Prospect | ProspectNo | Prospect | |
| PurchaseOrder | PONumber | PurchaseOrders | |
| Quote | QuoteID | Quotations | |
| ReturnVoucher | VoucherID | APVoucher | |
| ServiceAgreement | ID | ServiceAgreement | |
| ServiceDesk | LogHeaderID | LogHeader | |
| SubContract | SubContractCode | SubContracts | |
| SubContractorCetrtificationDetail | APInvoiceID.PONumber | SubcontractClaimValues | |
| Timesheet | PersonID.TimesheetDate | Timesheets | |
| WorksOrder |
...
| PONumber | PurchaseOrders |
Timesheet's RelatedRecordID has a Timesheet component, these need to be treated in the following way:
Format: yyyym(m)d(d)
As file names cannot contain slashes these have been removed. The year component is always 4 digits. The Month and Day component are variable length (One or two characters) as leading zeros are removed.
So a file being attached to PersonID 1234 for Week Ending 13/07/2012 would have a RelatedRecordID portion of the file name as:
1234.2012713
Rejected Files
Rejected files are files that could not be automatically attached for some reason.
...
The Config.ini is a TAB delimited file. However Commas cannot be used in this file, substituted for a pipe ( | ) character if required.
A resonable level reasonable knowledge of SQL is required to configure the Config.ini file correctly.
...