Inter-Scenario Data Access

I/O drivers

Driver scenariodata

scenariodata:SCENARIO_REPOSITORY_PATH_OR_ID

The driver can only be used in `initializations from' blocks. The SCENARIO_REPOSITORY_PATH_OR_ID must be either the repository path (of the form "/AppName/FolderName/ScenarioName") of the scenario from which data will be read, or the UID of that scenario. Within the initializations-from block you should specify the name of the local entity to populate, and the name of the external entity from which it will be populated, ie:

initializations from "mminsight.scenariodata:<repository path or id>"
 LOCAL ENTITY_NAME_1 as "ENTITY_NAME_1_IN_EXTERNAL_SCENARIO"
 LOCAL ENTITY_NAME_2 as "ENTITY_NAME_2_IN_EXTERNAL_SCENARIO"
 LOCAL ENTITY_NAME_3 as "ENTITY_NAME_3_IN_EXTERNAL_SCENARIO"
end-initializations

Both input and result entities can be read from the external scenario. There is a limitation on the number of external entities you can specify; if you see an error then try splitting the list of entities across multiple initializations from blocks. To access more than one scenario, use multiple initializations from blocks.

If the external scenario does not exist, or is not readable by the user executing the scenario, the model will abort with an error.

When the model is run from outside of Xpress Insight, attempting to use the scenariodata I/O driver will cause the model to abort with an error.

When running in Insight 5, updates to progress entities made by the insightsendprogress subroutine will not be available through the mminsight.scenariodata I/O driver.