Example Processes
There are a variety of processes where the use case is standard across a model. Below is a list of these example processes and their purposes.
Processes
Utility Processes
- Utility.Copy Scenario.Simple - copy data from a Scenario to a Scenario within a Cube.
- Utility.Copy Scenario.Extended - copy data from a Scenario to a Scenario within a Cube. Has expanded logic compared to Simple.
- Utility.Export.Cube to Table - export data from a Cube to a Table.
- Utility.Export.Cube to CSV - export data from a Cube to a CSV.
Dimension Processes
- System.Dimension.Time - create a Time dimension. This process exists in every MODLR server by default.
- Dimension.Date - create a Date dimension.
Mapping Processes
- Mapping.Time to Time.Month to Year Annual - create a mapping from month to annual elements in the Time dimension.
- Mapping.Time to Time.Month to Prior Month - create a mapping from month to prior month in the Time dimension.
- Mapping.Time to Date.Month to Month - create a mapping from an n-level Time element to the month parent in the Date dimension.
- Mapping.Date to Time.Date to Month - create a mapping from an n-level Date element to an n-level Time element.
- Mapping.Date to Date.Date to Prior Year Month - create a mapping from a Date element to the prior year's month parent element in the Date dimension.
- Mapping.Date to Date.Date to Prior Year Date - create a mapping from a Date element to the prior year's date element in the Date dimension.
INFO
The Mapping.Date processes rely on the Date dimension being built as per Dimension.Date. They also rely on the Time dimension having been built per the standard System.Dimension.Time process.
Build Processes
- Build.Time and Date Environment - runs the System.Dimension.Time and Dimension.Date dimension builds together with all the mappings between them, so both dimensions stay aligned on the same periods.
Microsoft Business Central Processes
The processes here enable quicker establishment of modelling with Microsoft Business Central. These processes can be configured further based on your needs.
- Business Central.Export.Company - Used for exporting Business Central
Companydata. All other exports depend on this process. It does not truncate the table — it only adds new entries. The values this process inserts are used as identifiers between tables, so the primary key of this table cannot be changed freely, as doing so may require realigning other tables that reference it. - Business Central.Export.Non Time Data - Used for exporting dimension data (dimension data in the data warehousing terminology, data that is not categorised by time). Commonly used for exporting data from Business Central Endpoints
Account,DimensionandDimensionData. - Business Central.Export.generalLedgerEntries - Used for for exporting
generalLedgerEntriesdata that is categorised by time (transaction data in the data warehousing terminology). - Business Central.Export.All - Runs all other Business Central processes required to maintain a model including:
- Business Central.Export.Company
- Business Central.Export.Non Time Data
- Business Central.Export.generalLedgerEntries
INFO
All process listed here require the Business Central Integration Library. All processes are built around Microsoft Business Central v2.0.
Salesforce Processes
- Salesforce Example - a rough example of a process connecting to Salesforce, making a basic request using the tokens from a Standard Integration.
INFO
This process requires a Standard Integration to have been set up with Salesforce - see Creating an Integration.
MYOB Processes
- MYOB AccountRight Example - an example of a process connecting to MYOB AccountRight, making a request using the tokens from a Standard Integration.
INFO
This process requires a Standard Integration to have been set up with MYOB - see Creating an Integration.
Xero Processes
- Xero Example - an example of a process connecting to Xero, listing the available organisations (tenants) for a connection and fetching each organisation's details.
INFO
This process requires a Standard Integration to have been set up with Xero - see Creating an Integration.
QuickBooks Processes
- QuickBooks Example - an example of a process connecting to QuickBooks, making a basic request using the tokens from a Standard Integration.
INFO
This process requires a Standard Integration to have been set up with QuickBooks - see Creating an Integration.
Procore Processes
- Procore Example - an example of a process connecting to Procore, making a basic request using the tokens from a Standard Integration.
INFO
This process requires a Standard Integration to have been set up with Procore - see Creating an Integration.
Chargebee Processes
- Chargebee Example - an example of a process connecting to Chargebee, authenticating with an API key and paging through results. This is an Advanced Integration.
Deel Processes
- Deel Example - an example of a process connecting to Deel, authenticating with an API token and client ID. This is an Advanced Integration.
Zambion Processes
- Zambion Example - an example of a process connecting to Zambion, including a small library that handles OAuth 2.0 client credentials authentication. This is an Advanced Integration.
ProcurePro Processes
- ProcurePro Example - an example of a process connecting to ProcurePro, including a small library that handles the access-token based authentication. This is an Advanced Integration.
PAYAPPS Processes
- PAYAPPS Example - an example of a process connecting to PAYAPPS, including a small library that handles the OAuth password grant and token refresh. This is an Advanced Integration.
NetSuite Processes
- NetSuite Process Example - an example of a process connecting to NetSuite's SuiteTalk REST API, including a small library that handles OAuth 1.0 request signing, querying the
accounttable via SuiteQL with pagination. This is an Advanced Integration. - NetSuite can also be connected as a Datasource using its own JDBC driver - see the NetSuite Datasource Example.
HammerTech Processes
- HammerTech Example - an example of a process connecting to HammerTech, including a small library that handles email/password/tenant authentication and paging through results. This is an Advanced Integration.
PropertyMe Processes
- PropertyMe Example - an example of a process connecting to PropertyMe, including a small library that handles its OAuth 2.0 refresh token flow. This is an Advanced Integration.
Eagle CRM Processes
- Eagle CRM Example - an example of a process connecting to Eagle CRM's GraphQL API, including a small library that handles token authentication and cursor-based pagination. This is an Advanced Integration.
Fixer Processes
- Fixer Example - an example of a process connecting to Fixer to pull historical foreign exchange rates. This is an Advanced Integration.
Sage MicrOpay Processes
- Sage MicrOpay Example - a simple example of a process connecting to Sage MicrOpay (Micropay Cloud API), including a small library that handles Basic Auth plus an API key header. This is an Advanced Integration.
ChatGPT Processes
- ChatGPT Example - a simple example of a process sending a prompt to ChatGPT and reading back the response. This is an Advanced Integration.
Claude Processes
- Claude Example - a simple example of a process sending a prompt to Claude via Anthropic's Messages API and reading back the response. This is an Advanced Integration.
Process Packages
Please refer to the documentation on Packages to utilise the process packages below.
- Time and Date Package Please click here to Download - contains the following processes:
- Build.Time and Date Environment
- Dimension.Date
- Mapping.Time to Time.Month to Year Annual
- Mapping.Time to Time.Month to Prior Month
- Mapping.Date to Time.Date to Month
- Mapping.Time to Date.Month to Month
- Mapping.Date to Date.Date to Prior Year Month
- Mapping.Date to Date.Date to Prior Year Date
- Business Central Integration Package. Please click here to Download - contains the following processes:
- Business Central.Export.All
- Business Central.Export.Company
- Business Central.Export.Non Time Data
- Business Central.Export.generalLedgerEntries
INFO
Processes listed as part of the Business Central Package require the Business Central Integration Library. This library require's configuration to the variables relating to your Business Central Environment