Difference between revisions of "Models"
Jump to navigation
Jump to search
(Created page with "Models are used as the security layer protecting your data and tying all ODataLink functionality together. Each model has a unique model code which forms part...") |
m (adding a new wiki page) |
||
| (13 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Models are used as the security layer protecting your data and tying all | Models are used as the security layer protecting your data and tying all OdataLink functionality together. | ||
Each model has a unique | Each model has a unique '''Model Code''' which forms part of the [[OData Feed URLs]]. | ||
Models are used to control: | Models are used to control: | ||
* to which [[Data Files|data files]] users will have access; | * which [[Users|users]] can access the model; | ||
* to which [[Endpoints|endpoints]] users will have access; | * to which [[Data Files|data files]] [[Users|users]] will have access; | ||
* | * to which [[Endpoints|endpoints]] [[Users|users]] will have access; | ||
* secure which [[IP Addresses]] are valid to access this data; | |||
We recommend you create a new model each time these requirements differ. | We recommend you create a new model each time these requirements differ. | ||
Each different type of data file requires a different type of model: | |||
* [[MYOB Models]] | |||
* [[Xero Accounting Models]] | |||
* [[Xero Assets Models]] | |||
* [[Xero Files Models]] | |||
* [[Xero Payroll (Australia) Models]] | |||
* [[Xero Payroll (New Zealand) Models]] | |||
* [[Xero Payroll (UK) Models]] | |||
* [[Xero Projects Models]] | |||
* [[Xero Practice Manager Models]] | |||
= Examples = | |||
You could create different models for '''Accounts Receivables''', '''Accounts Payables''' or '''Payroll''' staff. Doing so would ensure that sales staff cannot see sensitive payroll information. | You could create different models for '''Accounts Receivables''', '''Accounts Payables''' or '''Payroll''' staff. Doing so would ensure that sales staff cannot see sensitive payroll information. | ||
| Line 18: | Line 31: | ||
* [[Endpoints|Endpoints]] | * [[Endpoints|Endpoints]] | ||
* [[IP Addresses|IP addresses]] | * [[IP Addresses|IP addresses]] | ||
* [[Model Date Filters and Report Date Filters]] | |||
* [[When to create a new Model]] | |||
Latest revision as of 01:26, 3 February 2025
Models are used as the security layer protecting your data and tying all OdataLink functionality together.
Each model has a unique Model Code which forms part of the OData Feed URLs.
Models are used to control:
- which users can access the model;
- to which data files users will have access;
- to which endpoints users will have access;
- secure which IP Addresses are valid to access this data;
We recommend you create a new model each time these requirements differ.
Each different type of data file requires a different type of model:
- MYOB Models
- Xero Accounting Models
- Xero Assets Models
- Xero Files Models
- Xero Payroll (Australia) Models
- Xero Payroll (New Zealand) Models
- Xero Payroll (UK) Models
- Xero Projects Models
- Xero Practice Manager Models
Examples
You could create different models for Accounts Receivables, Accounts Payables or Payroll staff. Doing so would ensure that sales staff cannot see sensitive payroll information.