Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

When updating Data Model xml data, conditional settings will be lost. The parameter settings previously configured in the data model, are removed. This article will cover how to reset your parameter field data after refresh of data model data. 

NOTE: Every time you 'Retrieve' an updated xml for the Data Model that has these settings configured,  each setting MUST be re-configured, as this data is stored within the Data Model xml. By 'Retrieving' an updated xml, you are pulling new data from a stored procedure, change to the Data Model connection, etc. and all previous xml data is over written. 

Pre-Requisites

  1. Data Model based on a Stored Procedure with Parameters

Step-by-Step Guide

  1. Log into VISION
  2. In upper left corner, click on Settings.
  3. Select Manage Data Models/Connections
  4. Select the Data Model that requires field formatting to display lists, run a query, etc. Click on the Model Designer icon.

         

     5. Inside the Model Designer, on the Tables/Columns tab, there are 3 sections:

          a. Tables

          b. Columns

          c. Properties

     6. In the Columns sections, select the column that you want to present predefined data to the end user. Ex. in the image below, a predefined set of Divisions to allow the end user to select from a list has been defined. 


     7. Once you have selected the column to define, click on Configuration Default Editor, found beneath the Properties section. 

     8. A Value Editor box will be displayed. Select the type of display format that you will use to present the values to the end user. Ex. A query to a list in a table, a list created in the Value Editor, a Default Value, etc. 


         


     9. In this example, we will create a list in the Value Editor. This requires that we provide a Display value to end user as well as a value that will be used in the database when each of the display values are selected. Meaning, You may want to display the color name Red to the end user for selection, but the table will only recognize R for Red. You can add multiple items to present for the field selected, by clicking Add New at the bottom of the Value Editor box.

         

     10. After entering all desired values, click Save & Close button. 

     11. Sometimes, you will need to use a query to return the selection to a user, this is helpful for large lists that change frequently. In that situation, you can point to a database lookup to return the current list items as contained within the database. The lookup is created as a VISION Query based on another Data Model designed to provide lookup values from tables in the database.

     12. In the Value Editor, select Query as the Type and in the Query box, select which previously created VISION query that contains the values you are presenting to the end user. 

     13. In the Display column, click Select and choose the column that has the values to display to end user. In the Value column, choose the column that has the value to pass to the database when the user selects a display value. 

         


     14. When using a query to present values, you can only set up one query in the list for each field. 

     15. To set a default Text value, select Text as the Type and enter the value:

         


     16. You can force a Date or DateTime to be entered for a field. First set the data type on the right to the appropriate Date data type. 

         


NOTE: Every time you 'Retrieve' an updated xml for the Data Model that has these settings, each setting MUST be reconfigured, as this data is stored within the Data Model xml. By 'Retrieving' an updated xml, you are pulling new data from a stored procedure, change to the Data Model connection, etc. and all previous xml data is over written. 













































  • No labels