Creating the Name_All view

The Name_All view is a pseudo table, or concatenation, of multiple Name-related tables. It contains fields from all joined files, as well as all related rows from all joined files. An ID that does not have a row in all joined tables will not appear in the view.

The Name_All view automatically includes data from the Name and Name_Fin tables. It is required for all special pricing and should be used as a prefix for all iMIS source fields instead of the actual file name. (See Defining Special Pricing.) Any custom demographic table can be selected for inclusion in the view.

To create a Name_All view

  1. Determine the fields necessary for special pricing. If some of your special pricing fields come from a user-defined custom table:
    1. From Customers, select Set up module > General to open the Set up general options window.
    2. Click Additional Windows to open the Customer Setup - Additional Windows window.
    3. Click Define Tables to open the User Defined Tables window.
    4. Enable the Always Create and Use for Dues Pricing options for each table that includes a special pricing field. When these options are enabled, the Name_All view is automatically created after you click Save.
    5. Click Save.

    Note: You must be logged in as the database owner to perform this operation.

  2. Make sure a record exists for all IDs that will be billed at a special price.

    3. Note: If customer records were converted, or the Always Create option was activated before operations were live, you may need to generate the required missing user-defined records before you create the Name_All view. You can use a simple SQL script to do this.

    1. To enter the SQL script, select Utilities > SQL Query. The SQL Query window opens.
    2. Click New.
    3. Enter the script in the SQL Command Text area. 
      insert into Name_Demo(ID)
select ID from Name where not exists
(select Name_Demo.ID from Name_Demo where Name_Demo.ID = Name.ID)
    4. Click Execute.

    Note: You can add additional conditions such as customer type qualifications. Keep in mind that if you use a user-defined table in the Name_All view, the user-defined table must exist for every customer that is of a customer type being referenced in a special pricing formula.