This is absolutely exciting to see mr CognosPaul in action, hear his voice...thank you for your brilliant ideas and your valuable knowledge and skill..thank you PMsquare for making Cognos a better and more known product
Thanks for the great video. I think we need more videos like this one on how to use Report Studio. More videos like this will convince people that Report Studio is no longer something that only advanced report authors should have access to use and is no longer something that should be restricted from use nor something to be leery of.
Thanks for sharing. Good to see these kind of videos. These kinds of videos definitely helps democratize Cognos advanced reporting. Kudos to you Paul & PM2 team!
Always been a fan of your work, going back as far as some of the first Cognos 10 releases when I was a newbie consultant pretending he knew what he was doing.
Macros give you a huge range of additional options. Unlike standard prompt aliases (?P_Product?) prompt macros allow you to define default values and expression fragments. For example you could do something like: [Year] = #prompt('p_Year','integer',timestampMask($current_timestamp,'yyyy'))# If nothing is passed to the p_Year parameter the macro will default to the current year. You could also use query functions in there as well. [Year] = #prompt('p_Year','integer','year(getDate())')# Expression fragments are also a huge part of macros. Token prompts allow you to modify expressions with a parameter. Consider this: #prompt('topOrBottom','token','top')#Count([Regions],5,[Revenue]) the topOrBottom parameter, being a token, will turn that into topCount or bottomCount. Once you become comfortable with macros, I suspect you'll be using them far more often than aliases.
That being said there is exactly 1 usecase in which a prompt alias is better than a macro. Prompt aliases natively support in_range prompts, while macros do not.
@@PaulMendelson Hi There thanks for the upload. It is really helpful. I have created a column Let's say column 'A' in Frame work manager and for the column expression I used the promptmany function to capture the value selected by user in the runtime and passed it as parameter to a stored procedure. So the expression of Column A something like this in FM : Storedprocedure( Data Item 1, Data Item 2, promptmany()). Here Data item - 1 ans 2 are parameters of the stores procedure. Now coming to the main issue if i pull the newly created column A in Query Studio and run it as Excel/PDF/CSV a prompt page is created thanks to the usage of promptmany function in the column definition, after selecting a value from the prompt when click on OK nothing happens i just get a message in the screen saying Loading please wait then again back to the prompt page with no error . But the expected output is after clicking any value from the prompt it should generate the report file in the format that I have selected either (Excel/Excel data/PDF). However the report does run successfully in HTML format. Can you please tell me what shall i do to make the prompt work and be able to download the report output. One more thing I pulled the same column A to a list in report studio and able to generate report in Excel and PDF format. It is not working in Query Studio only. Please help me with this issue
@@prabhuprasadpanda2729 I honestly don't know what's going on there. Which version of Cognos are you using? Which browser? Query Studio has been out of support for a while, and it may be that the prompting mechanism Cognos uses no longer supports it. It also uses some quirks of Internet Explorer, so it doesn't always behave correctly in modern browsers. What I would do in this case is to open the browser developer toolbar, go to the network tab, and then look for browser requests going to the server. If there's a failed request, it would go a long way to explaining what's going on. It's been years since I've touched query studio. If you can set parameters directly onto the object, try doing that. It sounds like the error is happening during setting the parameter, so if we can bypass that point it should work.
Hi There thanks for the upload. It is really helpful. I have created a column Let's say column 'A' in Frame work manager and for the column expression I used the promptmany function to capture the value selected by user in the runtime and passed it as parameter to a stored procedure. So the expression of Column A something like this in FM : Stores procedure( Data Item 1, Data Item 2, promptmany()). Here Data item - 1 ans 2 are parameters of the stores procedure. Now coming to the main issue if i pull the newly created column A in Query Studio and run it as Excel/PDF/CSV a prompt page is created thanks to the usage of promptmany function in the column definition, after selecting a value from the prompt when click on OK nothing happens i just get a message in the screen saying Loading please wait then again back to the prompt page with no error . But the expected output is after clicking any value from the prompt it should generate the report file in the format that I have selected either (Excel/Excel data/PDF). However the report does run successfully in HTML format. Can you please tell me what shall i do to make the prompt work and be able to download the report output. One more thing a pulled the same column A to a list in report studio and able to generate report in Excel and PDF format. It is not working in Query Studio only. Please help me with this issue
This is absolutely exciting to see mr CognosPaul in action, hear his voice...thank you for your brilliant ideas and your valuable knowledge and skill..thank you PMsquare for making Cognos a better and more known product
Thanks for the great video. I think we need more videos like this one on how to use Report Studio. More videos like this will convince people that Report Studio is no longer something that only advanced report authors should have access to use and is no longer something that should be restricted from use nor something to be leery of.
Brilliant as always Paul. Some great features you highlighted there.
Thanks for sharing. Good to see these kind of videos. These kinds of videos definitely helps democratize Cognos advanced reporting. Kudos to you Paul & PM2 team!
Always been a fan of your work, going back as far as some of the first Cognos 10 releases when I was a newbie consultant pretending he knew what he was doing.
Why use prompt macro instead of the normal prompt parameter? Thanks for the answer in advanced.
Macros give you a huge range of additional options. Unlike standard prompt aliases (?P_Product?) prompt macros allow you to define default values and expression fragments.
For example you could do something like: [Year] = #prompt('p_Year','integer',timestampMask($current_timestamp,'yyyy'))# If nothing is passed to the p_Year parameter the macro will default to the current year. You could also use query functions in there as well. [Year] = #prompt('p_Year','integer','year(getDate())')#
Expression fragments are also a huge part of macros. Token prompts allow you to modify expressions with a parameter. Consider this: #prompt('topOrBottom','token','top')#Count([Regions],5,[Revenue]) the topOrBottom parameter, being a token, will turn that into topCount or bottomCount.
Once you become comfortable with macros, I suspect you'll be using them far more often than aliases.
That being said there is exactly 1 usecase in which a prompt alias is better than a macro. Prompt aliases natively support in_range prompts, while macros do not.
@@PaulMendelson Hi There thanks for the upload. It is really helpful. I have created a column Let's say column 'A' in Frame work manager and for the column expression I used the promptmany function to capture the value selected by user in the runtime and passed it as parameter to a stored procedure. So the expression of Column A something like this in FM : Storedprocedure( Data Item 1, Data Item 2, promptmany()). Here Data item - 1 ans 2 are parameters of the stores procedure. Now coming to the main issue if i pull the newly created column A in Query Studio and run it as Excel/PDF/CSV a prompt page is created thanks to the usage of promptmany function in the column definition, after selecting a value from the prompt when click on OK nothing happens i just get a message in the screen saying Loading please wait then again back to the prompt page with no error . But the expected output is after clicking any value from the prompt it should generate the report file in the format that I have selected either (Excel/Excel data/PDF). However the report does run successfully in HTML format. Can you please tell me what shall i do to make the prompt work and be able to download the report output. One more thing I pulled the same column A to a list in report studio and able to generate report in Excel and PDF format. It is not working in Query Studio only. Please help me with this issue
@@prabhuprasadpanda2729 I honestly don't know what's going on there. Which version of Cognos are you using? Which browser? Query Studio has been out of support for a while, and it may be that the prompting mechanism Cognos uses no longer supports it. It also uses some quirks of Internet Explorer, so it doesn't always behave correctly in modern browsers.
What I would do in this case is to open the browser developer toolbar, go to the network tab, and then look for browser requests going to the server. If there's a failed request, it would go a long way to explaining what's going on.
It's been years since I've touched query studio. If you can set parameters directly onto the object, try doing that. It sounds like the error is happening during setting the parameter, so if we can bypass that point it should work.
@@PaulMendelson Cognos Analytics 11.2.2 and On Chrome and Edge browser
Wow! Thank you very much!!!
Hi There thanks for the upload. It is really helpful. I have created a column Let's say column 'A' in Frame work manager and for the column expression I used the promptmany function to capture the value selected by user in the runtime and passed it as parameter to a stored procedure. So the expression of Column A something like this in FM : Stores procedure( Data Item 1, Data Item 2, promptmany()). Here Data item - 1 ans 2 are parameters of the stores procedure. Now coming to the main issue if i pull the newly created column A in Query Studio and run it as Excel/PDF/CSV a prompt page is created thanks to the usage of promptmany function in the column definition, after selecting a value from the prompt when click on OK nothing happens i just get a message in the screen saying Loading please wait then again back to the prompt page with no error . But the expected output is after clicking any value from the prompt it should generate the report file in the format that I have selected either (Excel/Excel data/PDF). However the report does run successfully in HTML format. Can you please tell me what shall i do to make the prompt work and be able to download the report output. One more thing a pulled the same column A to a list in report studio and able to generate report in Excel and PDF format. It is not working in Query Studio only. Please help me with this issue
Yeeeees... What beard oil do you use?