We have built a Clustered Master for one of our customers. From this Clustered Master a few Business Views are created.
The root table (the one at the top of the hierarchy) contains monthly data. This table is recreated every month and there are always 3 tables: this month, last month and the previous month.
The customer does not want to have to multiply by 3 the CMs nor the BVs.
Is there a way to use an Amper Variable in the access file of the CM? And, if so, when and how would a value be passed to it?

This message has been edited. Last edited by: Kerry,

There is a new feature in 7.7x where you can use variable in the master file. I was not aware of this feature before. The project I worked on customer data was stored in separate but identical views. Downside of this approach is that you have to manually edit the access and master files after you generate them to make them dynamic. Here is a link to documentation. Parameterizing Master and Access File Values Using Variables

Master File

  
FILENAME=VWREPORT, SUFFIX=SQLMSS, $
   SEGMENT=VWREPORT, SEGTYPE=S0, $
      FIELDNAME=COL_ID, ALIAS=COL_ID, USAGE=I11, ACTUAL=I4,$
      FIELDNAME=COL_NAME, ALIAS=COL_NAME, USAGE=A100V, ACTUAL=A100V, $
      VARIABLE NAME=&&CLNT_DB, DEFAULT='Dev_Reporting', $
      VARIABLE NAME=&&CLNT_SCH, DEFAULT='.dbo.', $
      VARIABLE NAME=&&CLNT_CONN, DEFAULT='RPT_DATA', $

Access File

  
SEGNAME=VWREPORT,
   TABLENAME=&&CLNT_DB|&&CLNT_SCH|vwMonthData, 
   CONNECTION=&&CLNT_CONN,
   KEYS=0, $

Environment Fex

-* File rpt_environment.fex
-* Set up reporting environment

-* Set the default values for database and database server.
-SET &&CLNT_DB = 'Reporting';
-SET &&CLNT_SRV = 'SQL1_PROD'

-* Overwrite data adapter to point to the appropriate database and database server.
ENGINE SQLMSS SET CONNECTION_ATTRIBUTES &&CLNT_CONN &&CLNT_SRV/,;&&CLNT_DB

Report Fex

-* File rpt_sample.fex

-INCLUDE rpt_environment.fex

TABLE FILE VWREPORT
PRINT
COL_ID
COL_NAME
END

Max,

Thanks for the knowledge share on the global variables within master and access files new feature.

We have cases were we've had two sets of files, one for each of two schemas.

From my testing, it looks like we will now be able to pass the schema into the access file programatically via a variable, thus we'd only need to maintain one set of files going forward.

Once again, many thanks,
Dave