I’m seeking your support with SAC hierarchy. It seems not working well when defining an input parameter in calculation view (CV) in hana studio.
Once added input parameter for years to enable users to select a specific year once they open the dashboard.
All hierarchies became not working & showing error as in screenshot.
SAC hierarchy error pic
Errors
Server Error Caught exception : exception 52731: Hierarchy cache error for hierarchy SBU_H : Hierarchy create error for
"_SYS_BIC"."FANAR_REPORTING_PROJECT.SCM.SAC_DATA_MODELS/CV_SCM_DELIVERY_AND_COST_MODEL/SBU_H/hier/SBU_H"
error: SQL: column store error: search table error: [34023]
Instantiation of calculation model failed;exception 306106: Undefined
variable: $$year_scope$$. Variable is marked as required but not
set in the query
I use YEAR_SCOPE input parameter in where statement to reduce the number of fetched records.
As you can see bellow this is the created YEAR_SCOPE.
SQL where statement with YEAR_SCOPE pic
This is how YEAR_SCOPE created
created YEAR_SCOPE in CV hana studio
Here from frontend side (SAC) by default 2019 is the selected value & user can change it as well
SAC frontend with year selection
At the end I’m wondering if there is any way to solve this error...
Thanks in advance!
In order to use input parameters with HANA information views it is required to use the WITH PARAMETERS() syntax.
When the view parameters have been defined as variables then the reporting UI will simply create WHERE conditions with the selection parameters chosen by the user.
Based on the screenshots this is what is happening here.
For SAC to instead use the WITH PARAMETERS syntax the view parameters have to be defined as input parameters and the parameters have to be mapped in SAC.
Related
In BQ I have saved view that connected to Data Studio. I need to add a parameter field to this view and control it from Data Studio.
Adding a dropdown list doesn't work, there is some complex calculations in BQ, i'm not getting the result i expected.
How i tried. Query, for example:
select *
from `project.dataset.table`
I added query parameter like this:
select *
from `project.dataset.table`
where subject = #subject
Then in Data Studio I added parameter field. But i'm getting this error message:
BigQuery error: Parameters are not supported; failed to parse view
How can I add parameter and connect view to Data Studio?
Use custom queries:
Choose Custom Query in BigQuery connector in Data Studio
Add the field as a parameter
BigQuery + DataStudio does support Query Parameter (as introduced here https://blog.google/products/marketingplatform/analytics/introducing-bigquery-parameters-data-studio/).
However, BigQuery itself doesn't support using using query parameter inside view definition. For now, you will have to leave the filter outside of the view.
How to write a Dynamic SQL query with bind/substitute variables in List and Labels report server?
When creating the Datasource I have the option to enter the query manually, but as soon I enter the bind an error message is displayed.
I want to be able to enter a dynamic query in the datasource and set the value of that bind/substitution variable.
This is something that's actively being worked on. This blog post covers the basics for parametrized data sources within List & Label itself. Thorough support within the Report Server, including support for stored procedure parameters, is on the roadmap and will be released this fall.
by processing (Process Full,Process Data) a table (every table) in my cube, I get the following error:
Failed to save modifications to the server. Error returned: 'A function 'MAX' has been used in a True/False expression that is used as a table filter expression. This is not allowed.
A function 'MAX' has been used in a True/False expression that is used as a table filter expression. This is not allowed.
The credentials provided for the SQL source are invalid. (Source at XXXX;XXXX.). The exception was raised by the IDbCommand interface.
How can I find which function cause this error?
Query the $SYSTEM.MDSCHEMA_MEASURES DMV, which lists measures in a Tabular model. The Expression column contains the definition of each measure, and you can use this to find any measures that have the MAX function that was specified in the error message. SSAS DMVs can either be queried from an MDX query editor window in SSMS or another tool such as Dax Studio. Dax Studio contains a listing of DMVs, and if you don’t already use it I’d recommend looking into this. You here find more information on this here. You can also execute your
measure in Dax Studio, which can help with
debugging it. You will also want to verify that the account you’re using has the proper permissions on the SQL Server objects used by your Tabular model.
While refreshing Webi report I am getting an error:
A database error occured. The database error text is: (CS) "Unexpected behavior" . (WIS 10901)
All the objects are parsing in the universe and Server is also responding. What can be the possible reason?
We are also able to run query in the database using database client tool.
If the error message appears after the a long time it might just be a timeout issue.
Else, you could try to import a version of the report that works in CMS to your local drive, rename it and run again.
It can be caused by some special character in the data combined with the fact that the server language settings do not foresee such character and therefore Business Objects cannot parse it for presentation.
If that is the case you might need to configure an environment variable of the server (like NLS_LANG) setting it to a value such that those special characters in your data can be handled by Business Objects.
In my situation, the error appera when some objet from the data base has changed or does not exists anymore. So we need to delete this object in the Universe or be sure that the field exists in the data base with the same name and type.
I had same problem with my reports. After couple hour of "investigation", I found.
I create Object in my universe, and set inappropriate type of object data Number, when value in database have type Character.
It throw me oracle Error (ORA-01722), and Bussiness Object error (WIS 10901), though SQL copied from report creator interface, executed directly on database return proper data.
I am developing an SSRS 2008 report, but instead of using stored procedures, I want to use all Text queries. This report was working with stored procedures, but when I changed this report to use same logic but via text queries, I got the following error:
An error occurred during local report processing
Query execution failed for dataset 'BRSR_Totals'
The variable name '#END_yEAR' has already been declared. Variable names must be unique within a query batch or stored procedure.
Operation cancelled by user.
The problem is that some of my datasets (text queries) re-use the same parameters and END_YEAR is one of these parameters. How do I make this report run correctly?
One area that you might want to check is case sensitivity. SSRS is case-sensitive when considering parameter names but T-SQL does not have that case sensitivity. Take another look at your code and make sure that all parameters are using the same case.
I just resolved a similar issue using a text query to populate a dataset. It worked in SQL Server Management Studio and it worked in the Query Designer within BIDS, but failed at runtime.
The issue turned out to be BIDS helpfully adding parameters to the Dataset that this query was referencing. Switching to the Parameters tab of the Dataset Properties showed that BIDS had duplicated the parameters I had already added earlier. Deleting the duplicates resolved my problem.
To respond to the suggestion that the logic be off-loaded into a stored procedure: in this case, the report is a custom report for a single customer. The query will only ever be used in this report and makes a few assumptions about the customer's configuration that should not be available globally
I also just fixed this same issue in one of my queries. I was using a text query and had datetime variables/parameters. SSRS added a second set into the parameters for the dataset properties. I deleted them and my query ran fine after that and my graph populated.
I ran into a similar issue on a report where I had declare a substantial number of parameters at the beginning that I didn't want the end user to see. The issue I had was I was using a comma at the beginning of the line, so I had:
DECLARE #Parameter VARCHAR(4) = 'text'
, #Parameter VARCHAR(4) = 'text2'
It worked just fine in SSMS, but when I ran it in Report Builder 3.0 it threw the error shown in this thread. I changed it to remove the comma and to restate DECLARE at the beginning of each line and it worked perfectly.
Check that you didn't declare it twice, once in the CREATE PROC statement you're creating and another in the actual code...I've seen this problem while testing changes to SP code.