Introduction to RASON
About RASON Models and the RASON Server
Rason Subscriptions
Rason Web IDE
Creating and Running a Decision Flow
Defining Your Optimization Model
Defining Your Simulation Model
Performing Sensitivity Analysis
Defining Your Stochastic Optimization Model
Defining Your Data Science Model
Defining Custom Types
Defining Custom Functions
Defining Your Decision Table
Defining Contexts
Using the REST API
REST API Quick Call Endpoints
REST API Endpoints
Decision Flow REST API Endpoints
OData Endpoints
OData Service for Decision Flows
Creating Your Own Application
Using Arrays, For, Loops and Tables
Organization Accounts

Model Names

RASON V2020 supports both named and unnamed models Note: A decision flow must be named. A model/flow becomes "named" either by including modelName: "name"/flowName: "name" in the RASON model text and then calling POST rason.net/api/model or by simply calling POST rason.net/api/model/<name> or both. Either call returns a Location header with a new resource ID that identifies this unique model instance. The "name" must be unique among models/flows with a user's account. An unnamed model, or a model not containing modelName, has no name.

  • A model/flow may be named by using a REST API call to POST rason.net/api/model/{name}, i.e. POST rason.net/api/model/TestModel2. See the example response below, note the resource ID ( 2590+TestModel2+2019-11-22-17-53-20-176350) that identifies the unique model instance.
          Location: https://rason.net/api/model/2590+TestModel2+2019-11-22-17-53-20-176350
      
      
  • A model may also be named by using the property modelName: "name" in the body of the RASON model. A decision flow may be named in a similiar manner by using the property flowName: "name". In the example code below, the model name is "TestModel1". The RASON model will be "named" with a call to POST rason.net/api/model or POST rason.net/api/model/{name}. If using POST rason.net/api/model/{name}, the name given to the modelName property and the name passed to POST rason.net/api/model/{name} must be identical, otherwise, an error will be returned. RASON model with modelName property

See the example response below, again, note the resource ID (2590+TestModel1+2019-11-22-18-25-40-015004) that identifies the unique model instance

    Location: https://rason.net/api/model/2590+TestModel1+2019-11-22-18-25-40-015004
  

The RASON Server maintains a simple, one-level directory of named models as ordinary text files using Azure file storage.

Additionally, a RASON model (standalone or reusable) may be saved to the user's OneDrive for Business account. If the model is stored in OneDrive for Business, the user must give the RASON server permission to access the account on OneDrive by adding a Data Connection on the MyAccount page at www.RASON.com.

Data Connections

For more information on creating a Data Connection, see the previous Data Connections topic. Note: There is a 4 MB limit on the size of files written back to OneDrive or OneDrive for Business.

Back to Resource IDs