The Infor CSI connector lets you extract data from Infor CSI into Dataddo and sync it to any dashboard, database, or data warehouse.
Refer to our website for the list of available metrics and attributes you can extract from Infor CSI.
If you have multiple Infor CSI accounts and would like to extract the same data from all of them, it's possible through multi-account extraction. Contact our Solutions team to enable this feature.
Data Coverage
Infor CSI exposes the following datasets. Each dataset maps to a table you can extract. Example fields are a representative sample; each dataset returns more columns.
| Dataset | Description | Example fields | Date range |
|---|---|---|---|
| Service Orders | Field service repair orders with status, customer, billing, cost, and scheduling data, filterable by record date. | SRO Number, Accumulated WIP, Allow Partial, Awaiting Parts, Bill Code, Bill Manager (+116 more) | Yes |
| Incidents | Field service incidents with status, priority, assigned SSR, customer, item, contact data, and SLA metrics. | Incident Number, Awaiting Parts, Bill To Name, Close Date, Contact, Create Date (+48 more) | Yes |
| Service Order Lines | Line-level detail for each service repair order, including type, status, billing, quantities, and cost breakdown per line. | SRO Number, SRO Line, Accumulated WIP, Awaiting Parts, Bill Code, Bill Status (+67 more) | Yes |
| Service Order Labor Transactions | Labor transactions posted against SRO lines, including hours worked, billing rates, operation codes, and partner reimbursement data. | SRO Number, SRO Line, SRO Operation, Transaction Number, Approved By, Approved Date (+65 more) | Yes |
| Service Order Material Transactions | Material transactions posted against SRO lines, including item, quantity, cost breakdown, WIP movements, and partner reimbursement data. | SRO Number, SRO Line, SRO Operation, Transaction Number, Approved By, Approved Date (+103 more) | Yes |
| Service Order Operations | Operations defined on service repair order lines, with status, scheduling, billing, and inspection data. | SRO Number, SRO Line, SRO Operation, Bill Code, Bill Status, Close Date (+15 more) | Yes |
| Service Order Transactions | Unified labor, material, and miscellaneous transactions posted against SRO lines, with costs, quantities, and event tracking. | SRO Number, SRO Line, SRO Operation, Transaction Number, Billing Code, Create Date (+24 more) | Yes |
| Service Customers | Field service customer records with billing details, contact information, address data, and financial summary metrics, one row per customer address sequence. | Customer Number, Customer Sequence, Apply Open Deposits, Bill Manager, Bill To Name, Contract Contact (+58 more) | Yes |
| Service Partners | Field service partners and technicians with contact details, availability hours, billing rates, GPS tracking data, and month-to-date performance metrics. | Partner ID, Active, Cost, Currency Code, Currency Code Description, Customer Number (+49 more) | Yes |
| Service Units | Installed units and equipment tracked in field service, with customer ownership, item details, maintenance schedule dates, and service history flags. | Serial Number, Item, Available for Rent, Available for Service, Bill To Name, Customer Order Line (+51 more) | Yes |
| Service Contracts | Service contract headers with customer, status, term dates, billing terms, and salesperson data. | Contract, Contract Status, Create Date, Customer Number, Customer Sequence, End Date (+6 more) | Yes |
| Service Schedules | Dispatch schedule and appointment records assigning partners to service jobs, expandable when scheduling data is available. | Sequence, Create Date, Partner ID, Schedule Date | Yes |
How Data Extraction Works
Every dataset for this connector uses a relative date range: the source reads a relative window (for example "last 7 days"), and that window slides forward with the current date. Every run re-reads the window, so a range of "1 day ago" always pulls the previous day (D-1). Each run replaces the window's data rather than adding older history. To load records from before the window, run a full data re-sync with a wider range. See Data Backfilling.
Set the relative date range when you create the source.
Metadata Columns
When you create a source, you can add these Dataddo metadata columns to the extracted data:
- dataddo_hash - a fingerprint built from each record's key fields. It works as a natural key, so it is ideal for upserts (updating existing rows in your destination instead of creating duplicates).
- dataddo_extraction_timestamp - the date and time the row was extracted. Use it to track how records change over time, for example to build slowly changing dimensions.
Sensitive Data
Datasets that contain personal data (for example names, email addresses, or phone numbers) can have those columns masked or hashed, so the raw values never leave Dataddo. Choose the columns to protect when you create the source.
How to Create an Infor CSI Data Source
Creating a data source takes you through six steps, shown in the progress bar at the top of the wizard. Each step is explained below.
1. Pick the connector
On the Sources page, click Create Source, then select the connector from the catalog. Use the search bar or the category tabs if you do not see it right away. You can rename the source at any time using the pencil icon next to its name.
2. Select the dataset
A dataset defines the shape of your data: which fields you get and how they relate. Select the dataset you want; you can still fine-tune the exact fields later.
- Each dataset has a short description of what it contains. Use the search box to find a dataset, attribute, or metric by name.
- The panel on the right previews the selected dataset's fields. For each field you can see its data type, whether it holds sensitive data (personal fields such as name or email are flagged), and which other datasets it links to, so you can see how the datasets relate.
3. Choose the account
This step selects what Dataddo reads from.
- Authorizer: Select an account you have already authorized from the drop-down. If you have none yet, choose Add new account and follow the prompts. If no authorizer is selected, Dataddo asks you to authorize before you continue.
- What to extract from: Select the exact entity you want to pull data from. Depending on the service this may be labelled an account, property, profile, workspace, or similar, sometimes with a sub-level to choose as well.
- Multiple accounts: To pull the same data from every entity you can access, turn on Automatically collect data from all .... This is multi-account extraction. Leave it off to choose them by hand.
4. Refine the attributes and metrics
The dataset already sets the structure. Here you fine-tune it: tick or untick the specific attributes and metrics you want to keep, and use the search box to find a field quickly. Click Test on Sample Data at any point to preview the result before you continue.
5. Add metadata columns (optional)
Two optional columns help your destination handle the data.
- Dataddo Hash (Include Row Hash): a fingerprint built from the columns you pick. It works as a natural key, so your destination can deduplicate rows and run upserts instead of creating duplicates. Turn it on, then select the columns that uniquely identify a row.
- Dataddo Extraction Timestamp: the time each row was extracted. Use it to watermark the data, for example to build slowly changing dimensions or to track when a value last changed.
6. Set the schedule
Decide how often Dataddo runs the extraction.
- Frequency: how often the pipeline runs, for example daily. Click Show advanced settings to also set the exact hour and minute (UTC).
- Date range: the relative window each run extracts, for example "Yesterday". The window moves forward on every run.
- Historical data: a new source starts from the current window. To load older data, run a full data re-sync after the source is created.
- Allow Empty Data Extractions: when on, a run that returns no data records zero rows instead of failing. Turn it on if the source can legitimately have periods with no data.
Click Save. Your data source is ready.
Related Articles
Now that you have successfully created a data source, see how you can connect your data to a dashboarding app or a data storage.
Sending Data to Dashboarding Apps
Sending Data to Data Storages
Other Resources