Difference between revisions of "Models"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
Models are used as the security layer protecting your data and tying all ODataLink functionality together. | 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: | Models are used to control: | ||
| Line 10: | Line 12: | ||
= Examples = | = 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. | ||
= Related Topics = | = Related Topics = | ||
Revision as of 17:54, 14 May 2020
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:
- to which data files users will have access;
- to which endpoints users will have access;
- and secure which IP Addressess are valid to access this data;
We recommend you create a new model each time these requirements differ.
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.