Is it possible to hide default member of Utility dimension, since I do not want to see it when I use the dimension in Excel pivot table.
I have tried to hide it in default perspective but then I am getting an error that default member is missing.
Edit:
I am using version 6.8.3. In the default perspective I have added following line:
-[Stats].[Stats].[L-Stats].[defaultMember]
After I successfully reloaded the cube, when I try to connect to it with Excel pivot table, I am getting an error: Missing default-member for hierarchy 'Stats(4)'
Related
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.
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.
I'm getting a strange error when exporting an Azure SQL Database. Exports had been working fine until some recent schema changes, but it's now giving me Error SQL71501.
The database is V12, Compatibility Level 130 (although the master database is still Compatibility Level 120).
The problem seems to be caused by a new table-valued function, which uses the built in STRING_SPLIT function. There were already stored procedures using STRING_SPLIT and they don't seem to have affected the export, but the function (which compiles OK, and is working fine) seems to cause a problem with the export.
The function below is a simplified version of the real one, but causes the same problem.
CREATE FUNCTION [dbo].[TestFunction](
#CommaSeparatedValues VARCHAR(MAX)
)
RETURNS TABLE
AS
RETURN
SELECT c.ClientId,
c.FullName
FROM dbo.Client c
INNER JOIN STRING_SPLIT(#CommaSeparatedValues, ',') csv
ON c.ClientId = csv.value
The complete error message given in the Import/Export history blade is as follows:
Error encountered during the service operation.
One or more unsupported elements were found in the schema used as part of a data package.
Error SQL71501: Error validating element [dbo].[TestFunction]: Function: [dbo].[TestFunction] has an unresolved reference to object [dbo].[STRING_SPLIT].
Error SQL71501: Error validating element [dbo].[TestFunction]: Function: [dbo].[TestFunction] contains an unresolved reference to an object. Either the object does not exist or the reference is ambiguous because it could refer to any of the following objects: [dbo].[Client].[csv], [dbo].[STRING_SPLIT].[csv] or [dbo].[STRING_SPLIT].[value].
This is Xiaochen from Microsoft SQL team. We are already working on the fix of this issue. The fix will be deployed to the export service in next few weeks. In the same time, the fix is already available in the latest DacFX 16.4 (https://blogs.msdn.microsoft.com/ssdt/2016/09/20/sql-server-data-tools-16-4-release/). Before we fix this issue in the service, you can download the DacFX 16.4 and use sqlpackage to work around.
SQLAzure validates Schema,references of the objects when you export database,if any of the references fails like the below one in your case
Error SQL71501: Error validating element [dbo].[TestFunction]: Function: [dbo].[TestFunction] has an unresolved reference to object [dbo].[STRING_SPLIT].
the export won't succeed..So you will need to resolve those errors,prior to export..
From the docs,you will need to set the compatibility level to 130
The STRING_SPLIT function is available only under compatibility level 130. If your database compatibility level is lower than 130, SQL Server will not be able to find and execute STRING_SPLIT function
Update:
I was able to repro the same issue and only current workaround is to delete the table valued function,that is referencing system function and export DACPAC,once export is done,recreate the table valued function :(
I have raised the issue here:please upvote..
https://feedback.azure.com/forums/217321-sql-database/suggestions/16722646-azure-database-export-fails-when-split-string-is-i
Data Migration Assistant did it for me. First run an assessment on the schema, on success, run your migration https://www.microsoft.com/en-us/download/details.aspx?id=53595/
I have an invalid column reference error in my sis package after editing my stored procedure with a case statement which added a column total sales from amount paid. Please can someone help with this? I cannot remap the columns in the package unless I resolve the error. Thanks
I faced a similar problem in my SSIS package. After adding a few new columns to my source table the "OLE DB Source" element would not map these new columns correctly either not displaying them at all on the mapping list or showing the "invalid column" error.
It turned out that the connection I was using had the RetainSameConnection parameter set to True (the package uses temp tables that are not to be dropped) - changing this to False enabled me to add the new columns to the mapping.
It might also be a good idea to check the DelayValidation and ValidateExternalMetadata parameters on elements connected to the data flow. These should probably be set to True in this case.
Perhaps someone runs into the same problem.
It seems that SSIS external metadata refresh is happened. If you change an underlying query that your SQL Server Integration Services (SSIS) package is relying on, you get the same message.
You can fix it by using Restore Invalid Column References Editor.Use this dialog box to restore the mappings of invalid column references. Set the Available Columns item to "" for all the entries and click OK. You should then be able to continue and remap the columns between source and destination.
If you couldn't see Restore Invalid Column References Editor then follow below steps.
Right-clicking the box with the warning sign
Selecting "Show Advanced Editor"
Activating "Column Mappings"
Clicking "Refresh"
Otherwise delete destination connection and rebuilding it from scratch.
I'm having the error one or more parameters required to run the report have not been specified. The only thing is i've removed all but one parameter from my report and I have specified the value for that parameter. My guess is it's still looking for one of the parameter's i deleted from the report. How do I find that parameter value and get rid of it?
Replacing reports on the server often does weird things with the parameters on the server. The fix is to delete the report off the server and then deploy a fresh version.
One way this can happen is if you are using Shared Datasets and you pull in DataSets that your report is not using. Each report must define its own version of the parameters for each shared Dataset locally. So if you've included a Dataset as one of your data sources and you have not explicitly defined how this particular report will pass parameters to that Dataset, you'll get this error.