robert fuschetto Posted September 3, 2021 Share Posted September 3, 2021 Set the stage We have a dashboard. It prompts for six parameters and renders a number of charts. Each chart has filters and each fex uses the SAME EXACT parameter names. Thus when the dashboard was built these parameters were auto set up and chained. Lets say one of the parameters is called DEPT. So each chart has a where condition on DEPT. DEPT is column name in the sql table and master file. Issue: We need to add a new chart. The chart will also filter on all 6 parameters however in the new data source the department field is called: DEPARTMENT. When I bring the chart onto the dashboard, WF creates a new parameter: DEPARTMENT. Problem: Obviously we do not want the user prompted for department twice (DEPT and DEPARTMENT) What can I do I cannot rename the column in the master file from DEPT to DEPARTMENT. There are too many other things connected to the master file. Thought: Can I define a column in the master file definition called DEPT and set its value to DEPARTMENT. If so can I then filter on this in my chart filter Will this solve my issue Is there a simpler waymaybe let WF create a new parameter=DEPARTMENT on the HTML page but somehow set it to the value held in DEPT that is already therethen hide DEPARTMENT so the user does not see it Note these are MULTI SELECTS if it matters. If so, how do I do this Other ideas Link to comment Share on other sites More sharing options...
Michael Meagher 2 Posted September 4, 2021 Share Posted September 4, 2021 Can you set the alias in your master to DEPT Link to comment Share on other sites More sharing options...
robert fuschetto Posted September 5, 2021 Author Share Posted September 5, 2021 will that still allow all fexes plumbed against DEPARTMENT to work Link to comment Share on other sites More sharing options...
Toby Mills Posted September 6, 2021 Share Posted September 6, 2021 I think your idea of using a DEFINE in the new master called DEPT thats equal to DEPARTMENT should work. I dont think you get away with using ALIAS as its highly likely you are hitting a SQL based table and the ALIAS is in use as the column name. Another thought is to manually edit the Master and change the FIELDNAME to DEPT while leaving the ALIAS =DEPARTMENT. This way, FOCUS will think of the fieldname is DEPT, and when the SQL is generated, itll generate with DEPARTMENT. The DEFINE essentially accomplishes the same thing. Link to comment Share on other sites More sharing options...
Azhar M A 2 Posted September 7, 2021 Share Posted September 7, 2021 Hi Robert, open new chart in Text Editor and find where condition WHERE DEPARTMENT EQ &DEPARTMENT Change to below WHERE DEPARTMENT EQ &DEPAT Thanks Azhar M A Link to comment Share on other sites More sharing options...
robert fuschetto Posted September 7, 2021 Author Share Posted September 7, 2021 Thanks TobyI like the idea of the new field. We have never done this. Hopefully I can figure out how to do itI recall it was in training at some part. Azhar, Not sure that will workwhen the HTML page was created the control was named: DEPT as this was the name in all the tables to thatpoint. The new table column is named: DEPARTMENT. If it hrow that chart on the HTML page it creates a new control: DEPARTMENT. Then the user is prompted for both DEPT and DEPARTMENT. Unless I am misunderstanding you Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now