Generateseries is not working with a parameter and single value slicer

[AmandaK]

I am trying to create a single value slicer 

I have created a parameter "Target Parameter" and a table "Target"

My parameter is "Target Parameter = GENERATESERIES(MIN(Target[Target]),MAX(Target[Target]))" (I have also tried adding the increment of 1 with the same result) the Target Table has 1 column with numbers from 0 to 1048576 generated from a linked excel file. Data type is Decimal Number but I have tried Whole and Fixed as well. 

When I look at the tables, I don't see any error in the sequenced numbers. 

When I enter a value such as 100000 into the associated slicer, the number in the slicer automatically changes to 99516

When I enter 2 it is automatically changed to 1

When I enter 1048570 is automatically changed to 1048576

Every number I have tried is changed to a different value except the largest number 1048576

Is there anyway to get it to accept and use the value entered? I intend to use the entered number in other calclations.

[123abc]

It seems like you're encountering unexpected behavior with the GENERATESERIES function when using it to define a parameter in Power BI.

The issue you're experiencing could be related to the way Power BI handles slicers and parameter values. Here are a few suggestions to troubleshoot and potentially resolve the problem:

1. Data Type Mismatch: Ensure that the data type of your parameter matches the data type of the values in your table. Since you mentioned that the Target table contains decimal numbers, make sure that the parameter is also defined as a decimal number.

2. Increment Specification: Since you've mentioned that you've tried adding an increment of 1, ensure that it's properly incorporated into your GENERATESERIES function. The syntax for including an increment is GENERATESERIES(start_value, end_value, [step_value]). If your aim is to generate a series from the minimum to the maximum value in your table with an increment of 1, it should look something like this: GENERATESERIES(MIN(Target[Target]), MAX(Target[Target]), 1).

3. Check for Filter Interactions: Sometimes slicers can be affected by interactions with other visuals on the report page. Check if there are any interactions set up that might be causing the unexpected behavior.

4. Verify Data Range: Double-check the range of values in your Target table to ensure there are no unexpected values or gaps in the sequence.

5. Test with Different Data: Create a simplified test case with a smaller dataset or synthetic data to see if you can replicate the issue. This can help isolate whether the problem is related to the specific dataset or a broader issue with your Power BI setup.

6. Update Power BI: Ensure you're using the latest version of Power BI Desktop. Sometimes, issues like this can be resolved with software updates that address bugs or introduce new features.

If none of these steps resolve the issue, it might be helpful to provide more specific details about your Power BI setup and the exact formula you're using for the parameter, which could aid in diagnosing the problem more accurately.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.

In case there is still a problem, please feel free and explain your issue in detail, It will be my pleasure to assist you in any way I can.