Report Builder keeps saying I have a parameter that I actually deleted
Hello, I am trying to build a report in Report Builder and have hit a snag. I am working with car insurance data. I have a boolean variable called "IsClaimOpen" that I turned into a parameter using my dataset Query Designer. (The values are Yes and No.) Report Builder called it "ClaimIsClaimOpen" by default. For clarity I went into the Parameter Properties and changed the name to simply "IsClaimOpen". All good so far, right? Wrong. When I ran the report, I received the following error message (with a buffering symbol and a "Loading..." message behind it): So I decided to go back and find out what the problem is. But not before playing around a little with the report. Once I got rid of the error message, the canvas showed me this error message: But I WAS able to select Yes or No from the parameter. If I hit "View Report", though, it would bring up the same error message as before, again with a buffering symbol and a "Loading..." message behind it. First I opened the Parameters folder on the the Report Data pane. There was one parameter there, labeled "IsClaimOpen". Then I went into the Dataset Properties window and then the Parameters section. Again, there was one parameter there, labeled "IsClaimOpen", with the expression "=Parameters!IsClaimOpen.Value(0)". I even tried running the report again, only to be taken to the same canvas as before. So I went back to Designer view and opened up Dataset Properties, because surely there was something I missed! I opened up Query Designer and browsed a bit, but I couldn't find anything. So I closed the Query Designer window and navigated to the Parameters tab of the Dataset Properties window. There I found the problem. There were two parameters listed. The second was named Is_Claim_Open and had the same expression as the one I named IsClaimOpen, but the first was called ClaimIsClaimOpen and was blank! I deleted this parameter immediately, and then ran the report again. But I got the same result as before. Does anyone have an idea what is causing this or how I can fix it? Thanks, Joe
How to get two enviroments in one workspace?
Hi, sorry for probably a stupid question, but all of this is new to me. We have created one workspace for a single report (as there is basically one user for it), which are DEV and PROD. The person who set it all up has left and I managed to mess things up. In the workspace, under the semantic model settings, there were two sets of parameters and data source credentials. Now there are just one. I have checked the Power BI desktop and there it still shows two different parameters for SQL Endpoint and Lakehouse. I did change name to SQL Endpoint and Lakehouse for two of the tables (from advanced settings), could that have messed things up?
Different column output basing on Parameter Selection
Hi Guys and Welcome Everyone! my first post in this community :). I have following query. I have created parameter using "New Parameter" -> "Numeric Range" Then I have edited parameter settings as follows: Then I would like to have column with different output depending on parameter selection. I wrote formula as follows: When I test it in report view, I always get "NOTPASSED", whatever I choose in the slicer. Do I miss anything or is there other workaround to achieve my goal?
Tabular Editor - Field Parameters - fields from more than 1 table
Hi Is it only possible to add fields from one table to create parametrs via Tabular Editor? In Analysis Services connected to a date warehouse I have various dimesnions which I would like to be selectable (customer, state, channel, salesperson etc). I have tried using the C# script posted by Daniel Otykier however seems it is limited to selecing fields from 1 table only. Is this correct?
Power BI Report Builder - Distinct Parameter Values while maintaining Data Model
Hello, I have read so many blog/ forum posts on this but I can't for the life of me get this working, so I really appreciate any help. I am creating a Paginated Report, which is linked to a Power BI Dataset that has two tables which are linked together. I want cascading parameters, and this works if I add the parameters by right clicking the Parameters folder and selecting Add Parameter, then getting Available Values from a Query pointing to the relevant table . Done this way, the selection I make in my first parameter limits the options available in the second (yay) EXCEPT that the values in the parameter drop down are not DISTINCT, so I literally have the same option appearing 20+ times: If I add the parameter when creating my datasets (by dragging a field into the Parameters section in the Query Designer) then I get DISTINCT values, but the first parameter no longer filters the second. To try and resolve this I have created separate tables that have DISTINCT values using a Query like the below: DEFINE VAR DistinctValuesTable = SUMMARIZE ( FILTER ( 'EntityGroup', EntityGroup[Organisation] = SELECTEDVALUE(@EntityGroupOrganisation) ), 'IndicatorHandbook'[Corporate Plan / Annual Report] ) EVALUATE DistinctValuesTable Then I set the Available Values for the parameter to this table, which does remove duplicates but the issue remains that the options in subsequent parameters are not affected by earlier selections. Any help would be greatly appreciated. I can't figure out why this would be so difficult, surely no-one wants the parameter options to work this way by default?!
