Editing a model's details: Difference between revisions

From OdataLink
Jump to navigation Jump to search
← Older editNewer edit →
No edit summary
No edit summary
Line 14: Line 14:
# Enter the '''Model Code''';
# Enter the '''Model Code''';
#: The ''secret'' code which will form part of the [[OData Feed URLs|OData feed url]]. It must be unique for your [[Account|account]]. Changing it will ''break'' any [[OData Feed URLs|OData feed url]] in use. This may be useful if concerned that an [[OData Feed URLs|OData feed url]] has been compromised or sent to the wrong individual. If you decide to change it, note that it must be at most 20 characters long. Only letters, numbers dashes and spaces are allowed.
#: The ''secret'' code which will form part of the [[OData Feed URLs|OData feed url]]. It must be unique for your [[Account|account]]. Changing it will ''break'' any [[OData Feed URLs|OData feed url]] in use. This may be useful if concerned that an [[OData Feed URLs|OData feed url]] has been compromised or sent to the wrong individual. If you decide to change it, note that it must be at most 20 characters long. Only letters, numbers dashes and spaces are allowed.
#;<br \>Data File Options
 
# Configure the '''Data File Options'''.
# Configure the '''Data File Options'''.
#; ''Note: The [[Model Type|Data File Type]] cannot be changed once a model has been created.''
#; ''Note: The [[Model Type|Data File Type]] cannot be changed once a model has been created.''
## Tick/untick the '''Consolidation Allowed''' checkbox;
## Tick/untick the '''Consolidation Allowed''' checkbox;
##: Controls whether the '''Consolidation''' OData feed is available or not.
##: This option controls whether the [[Consolidation OData Feed|Consolidation OData feed]] is available or not.
#;<br \>Security Options
 
# Choose the [[Login Types|Login Type]] required to access the data.
# Configure the Security Options
#: '''Basic''' login will require the username and password of a [[Users|user]] when accessing data.
## Choose the [[Login Types|Login Type]] required to access the data.
#: '''Anonymous''' will not require any credentials when accessing data.
##: '''Basic''' login will require the username and password of a [[Users|user]] when accessing data.
# Tick/untick the '''Firewall Enabled''' checkbox;
##: '''Anonymous''' will not require any credentials when accessing data.
#: Controls whether the Firewall is active and protecting your data via a list of authorised [[IP Addresses]].
## Tick/untick the '''Firewall Enabled''' checkbox;
# Tick/untick the '''Enabled''' checkbox;
##: Controls whether the Firewall is active and protecting your data via a list of authorised [[IP Addresses]].
#: Controls whether all [[OData Feed URLs|OData feed urls]] for this [[Models|model]] are usable.
## Tick/untick the '''Enabled''' checkbox;
#;<br \>Performance Options
##: Controls whether all [[OData Feed URLs|OData feed urls]] for this [[Models|model]] are usable.
# Choose the [[Archive Types|Archive Type]].
 
#: '''Live''' optimises the model for live use.
# Configure the Performance Options
#: '''Live (no archive)''' provides access to data without caching any information (worse performance).
## Choose the [[Archive Types|Archive Type]].
#: '''Developer''' optimises the model for development is faster but refreshes are once every 8 hours
##: '''Live''' optimises the model for live use.
#: '''Static''' optimises the model for historica data that never changes.  
##: '''Live (no archive)''' provides access to data without caching any information (worse performance).
# If using the '''Live''' [[Archive Types|archive types]], you can also configure whether to archive old historical data. You can do so by choosing how the '''Cut Off Date''' is calculated.
##: '''Developer''' optimises the model for development is faster but refreshes are once every 8 hours
#:  '''Do not archive data by date''' disables the archiving mechanism except for specific endpoints.
##: '''Static''' optimises the model for historica data that never changes.  
#:  '''Archive data prior to cut off date''' archives any data created prior to the cut off date entered.
## If using the '''Live''' [[Archive Types|archive types]], you can also configure whether to archive old historical data. You can do so by choosing how the '''Cut Off Date''' is calculated.
#:  '''Archive data prior X months''' archives any data created prior to the cut off date calculated from the number of months entered.
##:  '''Do not archive data by date''' disables the archiving mechanism except for specific endpoints.
#:  '''Archive data prior X days''' archives any data created prior to the cut off date calculated from the number of days entered.
##:  '''Archive data prior to cut off date''' archives any data created prior to the cut off date entered.
# Choose the [[Archive Paging|Archive Paging]].
##:  '''Archive data prior X months''' archives any data created prior to the cut off date calculated from the number of months entered.
#: '''Default''': OdataLink will page the date as requested.
##:  '''Archive data prior X days''' archives any data created prior to the cut off date calculated from the number of days entered.
#: '''By Month''': OdataLink will page the data one calendar month at a time. This may increase the performance for VERY LARGE data files.
## Choose the [[Archive Paging|Archive Paging]].
#: '''By Year''': OdataLink will page the data one calendar year at a time. This may increase the performance for LARGE data files.
##: '''Default''': OdataLink will page the date as requested.
# Enter a [[Default Date Range]] to control how much data is retrieved.
##: '''By Month''': OdataLink will page the data one calendar month at a time. This may increase the performance for VERY LARGE data files.
#: These dates will apply when no date filters are applied via the [[OData client]].
##: '''By Year''': OdataLink will page the data one calendar year at a time. This may increase the performance for LARGE data files.
# If applicable, enter the [[Default Page Size]].
## Enter a [[Default Date Range]] to control how much data is retrieved.
#: This controls the number of records that will be returned on a single call for most endpoints^.
##: These dates will apply when no date filters are applied via the [[OData client]].
#;<br \>Miscellaneous Options
## If applicable, enter the [[Default Page Size]].
# Choose the [[OData Client Compatibility|OData Client Compatibility]] option required.
##: This controls the number of records that will be returned on a single call for most endpoints^.
#: We recommend leaving this setting as ''(Auto Detect)''.
 
# Configure the Miscellaneous Options
## Choose the [[OData Client Compatibility|OData Client Compatibility]] option required.
##: We recommend leaving this setting as ''(Auto Detect)''.
# Click '''Save'''.
# Click '''Save'''.


Revision as of 23:05, 18 June 2025

By editing a model's details, you will be able to configure it's Name and Model Code.


Steps

To edit's a model's details, follow these steps.

  1. Click on Models on the menu in the left-hand side;
  2. Find the model you want to work on and click View;
  3. Select the Settings tab;
  4. Click on the Edit Model button;
  5. Enter the Model Name;
    This is the display name of the model and is only used within the OdataLink website.
  6. Enter the Model Code;
    The secret code which will form part of the OData feed url. It must be unique for your account. Changing it will break any OData feed url in use. This may be useful if concerned that an OData feed url has been compromised or sent to the wrong individual. If you decide to change it, note that it must be at most 20 characters long. Only letters, numbers dashes and spaces are allowed.
  1. Configure the Data File Options.
    Note: The Data File Type cannot be changed once a model has been created.
    1. Tick/untick the Consolidation Allowed checkbox;
      This option controls whether the Consolidation OData feed is available or not.
  1. Configure the Security Options
    1. Choose the Login Type required to access the data.
      Basic login will require the username and password of a user when accessing data.
      Anonymous will not require any credentials when accessing data.
    2. Tick/untick the Firewall Enabled checkbox;
      Controls whether the Firewall is active and protecting your data via a list of authorised IP Addresses.
    3. Tick/untick the Enabled checkbox;
      Controls whether all OData feed urls for this model are usable.
  1. Configure the Performance Options
    1. Choose the Archive Type.
      Live optimises the model for live use.
      Live (no archive) provides access to data without caching any information (worse performance).
      Developer optimises the model for development is faster but refreshes are once every 8 hours
      Static optimises the model for historica data that never changes.
    2. If using the Live archive types, you can also configure whether to archive old historical data. You can do so by choosing how the Cut Off Date is calculated.
      Do not archive data by date disables the archiving mechanism except for specific endpoints.
      Archive data prior to cut off date archives any data created prior to the cut off date entered.
      Archive data prior X months archives any data created prior to the cut off date calculated from the number of months entered.
      Archive data prior X days archives any data created prior to the cut off date calculated from the number of days entered.
    3. Choose the Archive Paging.
      Default: OdataLink will page the date as requested.
      By Month: OdataLink will page the data one calendar month at a time. This may increase the performance for VERY LARGE data files.
      By Year: OdataLink will page the data one calendar year at a time. This may increase the performance for LARGE data files.
    4. Enter a Default Date Range to control how much data is retrieved.
      These dates will apply when no date filters are applied via the OData client.
    5. If applicable, enter the Default Page Size.
      This controls the number of records that will be returned on a single call for most endpoints^.
  1. Configure the Miscellaneous Options
    1. Choose the OData Client Compatibility option required.
      We recommend leaving this setting as (Auto Detect).
  2. Click Save.


Notes

^In Xero, Paginanation is supported by some, but not all, endpoints. Xero Reference.
For a comprehensive list of Xero and MYOB endpoints that support pagination, please refer to Default Page Size.

Related Topic

Configuring models

Retrieved from "https://help.odatalink.com/index.php?title=Editing_a_model%27s_details&oldid=4391"